On 3/8/2019 10:44 AM, Rahul Goswami wrote:
1) Is there currently a configuration setting in Solr that will trigger the first option you mentioned ? Which is to not serve any searches until tlogs are played. If not, since instances shutting down abruptly is not very uncommon, would a JIRA to implement this configuration be warranted?
In what setup is an abrupt shutdown *expected*? If that's really common, then your setup is, in my opinion, very broken. It is our intent that abrupt death of the Solr process should be quite rare. We do still have a problem on Windows where the wait for clean shutdown is only five seconds -- nowhere near enough. The Windows script still needs a lot of work, but most of us are not adept at Windows scripting.
There is an issue for the timeout interval in bin\solr.cmd on Windows: https://issues.apache.org/jira/browse/SOLR-9698
2) We have a setup with moderate indexing rate and moderate search rate. Currently the auto commit interval is 10 mins. What should be a recommended hard commit interval for such a setup? Our concern with going too low on that autoCommit interval (with openSearcher=false) is the number of segments that would drastically increase, eventually causing merges,slower searches etc.
Solr has shipped with a 15 second autoCommit, where openSearcher is set to false, for a while now. This is a setting that works quite well. As long as you're not opening a new searcher, commits are quite fast. I personally would use 60 seconds, but 15 seconds does work well. It is usually autoSoftCommit where you need to be concerned about short intervals, because a soft commit opens a searcher.
Thanks, Shawn
