Re: [Solr-5-4-1] Why SolrCloud leader is putting all replicas in recovery at the same time ?

2016-10-13 Thread Gerald Reinhart
Hi Pushkar Raste, Thanks for your hits. We will try the 3rd solution and keep you posted. GĂ©rald Reinhart On 10/07/2016 02:23 AM, Pushkar Raste wrote: A couple of questions/suggestions - This normally happens after leader election, when new leader gets elected, it will force all the

Re: [Solr-5-4-1] Why SolrCloud leader is putting all replicas in recovery at the same time ?

2016-10-07 Thread Petetin Ludovic
Hi Erick, thanks for taking time to answer. What we are looking for here is not the root cause but a mechanism to prevent the leader from doing this silly thing of putting all the replicas in recovery at the same time which inevitably leads to a downtime. Is there a similar conf in Solr as

Re: [Solr-5-4-1] Why SolrCloud leader is putting all replicas in recovery at the same time ?

2016-10-06 Thread Pushkar Raste
A couple of questions/suggestions - This normally happens after leader election, when new leader gets elected, it will force all the nodes to sync with itself. Check logs to see when this happens, if leader was changed. If that is true then you will have to investigate why leader change takes

Re: [Solr-5-4-1] Why SolrCloud leader is putting all replicas in recovery at the same time ?

2016-10-06 Thread Erick Erickson
There is no information here at all that would us to say anything meaningful. You might review: http://wiki.apache.org/solr/UsingMailingLists What do the logs say? Are there any exceptions? What happens on your system that's unusual if anything? In short, what have you tried to do to diagnose the

[Solr-5-4-1] Why SolrCloud leader is putting all replicas in recovery at the same time ?

2016-10-06 Thread Gerald Reinhart
Hello everyone, Our Solr Cloud works very well for several months without any significant changes: the traffic to serve is stable, no major release deployed... But randomly, the Solr Cloud leader puts all the replicas in recovery at the same time for no obvious reason. Hence, we