On 6/9/23 03:05, Nick Vladiceanu wrote:
autoCommit is enabled and it also has openSearcher set to true because in TLOG / PULL replicas there is no softCommit and therefore we need to open a new searcher during autoCommit.<autoCommit> <maxTime>${solr.autoCommit.maxTime:300000}</maxTime> <maxDocs>${solr.autoCommit.maxDocs:1000}</maxDocs> <openSearcher>true</openSearcher> </autoCommit> When tried to reload the collection, the node in question (node-7) timed out without any errors (general timeout, 180s).
You should probably lower the maxTime on your autoCommit. Unless you have commits that regularly take longer than 30 seconds to complete ... and if that's the case, you might have a general performance issue and it might not be easy to solve. I would suggest a value of 60000 for maxTime.
You should also remove maxDocs. Time based autoCommit is a lot more predictable. With a super low value of 1000 docs, the autoCommit may be firing VERY frequently, and that can be problematic.
With the relatively small size of your indexes, it seems very weird that a reload would take longer than 3 minutes. I would expect it to take at most a few seconds. I managed a sharded index (no SolrCloud) with much larger cores and reloading all the cores would only take a few seconds total. We're back to the possibility of a general performance issue.
I am hoping that all the fixes in 9.2.1 will help. I did a quick glance through CHANGES.txt and nothing jumped out at me as a definite candidate for your troubles, but sometimes multiple fixes work together to fix a larger issue.
I wish I had something more definite to tell you. Are you seeing any warnings or errors in solr.log?
Thanks, Shawn
