2
Indexing Service
Question asked by Rafael Grecco - 6/18/2015 at 8:33 AM
Answered
Hi,
 
I am having a issue with indexing service in one of my smartermail servers.
 
This particuar server is the one that have the highest amount of traffic of all my servers (I have 4 in total).
 
It has 220 domains and 3000 users.
 
The problem is that the indexing service runs non stop, and using default options, it will slow down the server a lot. The interface gets a little delay, the spool gets 2 or 3 times bigger and SMTP connections sometimes don't work on the first try.
 
As soon as I disable indexing service, everything starts to run lightning fast. I did change the indexing maximum threads to 2 (down from 6) and this way it doesn't affect server performance, but it wont keep up with the amount of indexing necessary.
 
Is there a way to schedule indexing on and off or change the number of max threads based on time or server performance?
 
I know that what I am asking would require coding. But something more simple as: "At 7 pm starts index service and at 7 am stops indexing service" would greatly help me. Has anyone ever done it?
 
Thanks!

9 Replies

Reply to Thread
0
Bruce Barnes Replied
SmarterMail version and server configuration?
Bruce Barnes ChicagoNetTech Inc brucecnt@comcast.net Phonr: (773) 491-9019 Phone: (224) 444-0169 E-Mail and DNS Security Specialist Network Security Specialist Customer Service Portal: https://portal.chicagonettech.com Website: https://www.ChicagoNetTech.com Security Blog: http://networkbastion.blogspot.com/ Web and E-Mail Hosting, E-Mail Security and Consulting
0
Rafael Grecco Replied
SM version 11
8 2,2GHz processors
8Gb RAM
RAID10 configuration
2
Employee Replied
Employee Post
Rafael, it definitely sounds like your RAID is running into a bottleneck situation.  There was an issue with indexing that has been fixed in SM 12+ in which in some cases the indexing would be caught in an infinite loop which caused high CPU usage and thus sluggish UI responsiveness.
 
Are you running the server locally or on a SAN?  There are known issues with SAN configurations.  You may want to consider opening a support ticket so we can more deeply examine the issue.
 
As for configuring the indexing to run only during specific times, this would be a feature request.
0
Rafael Grecco Replied
Hey Webio, I had already read those posts. I already upvoted them :)
0
Rafael Grecco Replied
Hi Robert,
 
Maybe the RAID is the bottleneck. If that is the case, I don't have many alternatives.
 
"As for configuring the indexing to run only during specific times, this would be a feature request." - Is this on your list of requested features already?
 
Thanks for your answer.
0
Employee Replied
Employee Post
Rafael, I have added your suggestion of running the index service at a specified times to our features request list. Please note that any new messages that have not been indexed will not be searchable until they are indexed.
0
Employee Replied
Employee Post
Rafael, can you check your indexing log and see if any particular account is having issues or if there are any errors in the log?
2
Rafael Grecco Replied
Marked As Answer
Hi Robert,
 
I just found out that the indexing queue is actually smaller than before.
 
At the default value of 6 indexing threads, the server was so slow that the indexing queue had a lot of accounts, and the indexing process was taking some time.
 
Now, at 2 max threads, the queue is actually a third of the size it was before. It is interesting that making a change that I believed would make things eventually worse (like getting a huge queue), made everything faster.
 
Anyway, there are no errors. Everything is running smoothly now.
 
I hope this info helps if someone have the same problem!
 
Thanks
Rafael

Reply to Thread