Solr will not go down due to “performance warning”. All that means is that you’re opening too many searchers in a short time. If you’re somehow opening a huge number of searchers, then maybe but IIRC you can’t really open more than two. And don’t think you can “fix” this by upping maxWarmingSearchers, that’ll only make the problem worse as every new searcher chews up memory that’s kept until the old searcher is done with outstanding requests.
Which is weird because with those settings you shouldn’t be opening _any_ new searchers. So my guess is that some external client is doing that and this is usually an anti-pattern. Don’t do it, please. Just set your soft commit to what you need and leave it at that. As long as possible. Here are all the gory details: https://lucidworks.com/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/ I’d also not bother with maxDocs, that’s much less predictable than just setting a reasonable time for autocommit, a minute or two is usually reasonable especially when openSearcher is false. Not sure what’s really generating that error, take a look at all your other Solr logs to see if there’s a cause. Best, Erick > On Apr 10, 2019, at 5:21 AM, vishal patel <vishalpatel200...@outlook.com> > wrote: > > I have 2 shards and 2 replicas of Solr 6.1.0. one shard and one replica went > down and I got below ERROR > > 2019-04-08 12:54:01.469 INFO (commitScheduler-131-thread-1) [c:products > s:shard1 r:core_node1 x:product1] o.a.s.s.SolrIndexSearcher Opening > [Searcher@24b9127f[product1] main] > 2019-04-08 12:54:01.468 INFO (commitScheduler-110-thread-1) [c:product2 > s:shard1 r:core_node1 x:product2] o.a.s.c.SolrDeletionPolicy > SolrDeletionPolicy.onCommit: commits: num=2 > commit{dir=G:\SolrCloud\solr1\server\solr\product2\data\index.20180412060518798,segFN=segments_he5,generation=22541} > commit{dir=G:\SolrCloud\solr1\server\solr\product2\data\index.20180412060518798,segFN=segments_he6,generation=22542} > 2019-04-08 12:54:01.556 INFO (commitScheduler-110-thread-1) [c:product2 > s:shard1 r:core_node1 x:product2] o.a.s.c.SolrDeletionPolicy newest commit > generation = 22542 > 2019-04-08 12:54:01.465 WARN (commitScheduler-136-thread-1) [c:product3 > s:shard1 r:core_node1 x:product3] o.a.s.c.SolrCore [product3] PERFORMANCE > WARNING: Overlapping onDeckSearchers=2 > > 2019-04-08 12:54:01.534 ERROR > (updateExecutor-2-thread-36358-processing-http:////10.101.111.80:8983//solr//product3 > x:product3 r:core_node1 n:10.102.119.85:8983_solr s:shard1 c:product3) > [c:product3 s:shard1 r:core_node1 x:product3] o.a.s.u.StreamingSolrClients > error > org.apache.solr.common.SolrException: Service Unavailable > > request: > http://10.101.111.80:8983/solr/product3/update?update.distrib=FROMLEADER&distrib.from=http%3A%2F%2F10.102.119.85%3A8983%2Fsolr%2Fproduct3%2F&wt=javabin&version=2 > at > org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrClient$Runner.sendUpdateStream(ConcurrentUpdateSolrClient.java:320) > at > org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrClient$Runner.run(ConcurrentUpdateSolrClient.java:185) > at > org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$22(ExecutorUtil.java:229) > at > org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor$$Lambda$3/30175207.run(Unknown > Source) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > > Note : product1,product2 and product3 are my collection. > > In my solrconfig.xml > <autoCommit> > <maxTime>600000</maxTime> > <maxDocs>20000</maxDocs> > <openSearcher>false</openSearcher> > </autoCommit> > > <autoSoftCommit> > <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime> > </autoSoftCommit> > <maxWarmingSearchers>2</maxWarmingSearchers> > > There are many documents committed at that time and I found out so many > commitScheduler threads in Log. > Solr went down due to warn PERFORMANCE WARNING: Overlapping onDeckSearchers=2 > is it possible? > Need to update my autoCommit or maxWarmingSearchers? > > Sent from Outlook<http://aka.ms/weboutlook>
