[ https://issues.apache.org/jira/browse/SOLR-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897936#comment-16897936 ]
Alexander S. commented on SOLR-6769: ------------------------------------ Hi, unfortunately I can't test with the latest versions since we are tied to Solr 5. I tuned our caches and didn't see this error any more so let's close for now. > Election bug > ------------ > > Key: SOLR-6769 > URL: https://issues.apache.org/jira/browse/SOLR-6769 > Project: Solr > Issue Type: Bug > Reporter: Alexander S. > Priority: Major > Attachments: Screenshot 876.png > > > Hello, I have a very simple set up: 2 shards and 2 replicas (4 nodes in > total). > What I did is just stopped the shards, but if first shard stopped immediately > the second one took about 5 minutes to stop. You can see on the screenshot > what happened next. In short: > 1. Shard 1 stopped normally > 3. Replica 1 became a leader > 2. Shard 2 still was performing some job but wasn't accepting connection > 4. Replica 2 did not became a leader because Shard 2 is still there but > doesn't work > 5. Entire cluster went down until Shard 2 stopped and Replica 2 became a > leader > Marked as critical because this shuts down the entire cluster. Please adjust > if I am wrong. -- This message was sent by Atlassian JIRA (v7.6.14#76016) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org