You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my case the option max_children with the value 0 doesn't work properly. After some time of work the searchd daemon is freezing and do not respond to connections. This is the part of my config file:
workers = fork depricated long time ago, daemon uses thread worker in this case and as you set max_children = 0 daemon does not constrain incoming connection and might lead to box run out of resource.
Could you provide searchd.log there I could see event around hung time?
Could you also attach to hung daemon with gdb issue command thread apply all bt and provide its output here?
In case you do not want to constrain amount of incoming clients you might switch to worker = thread_pool and set option of max_children around 1.2 * CPU cores . This way daemon will handle all incoming connection however uses thread pool for processing up to max_children threads.
It is not very clear wheather you need any help or not, so I'm closing the issue for a while. You can always re-open it, if you'd have more questions. Thank you
In my case the option max_children with the value 0 doesn't work properly. After some time of work the searchd daemon is freezing and do not respond to connections. This is the part of my config file:
When i set max_children the exact value everything is fine.
I'm using Manticore 2.4.1 3b31a97@171017 id64-release
What is going wrong? Is it a bug or i need to specify some other options? Hope on your responce.
The text was updated successfully, but these errors were encountered: