lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Rafalovitch (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SOLR-6769) Election bug
Date Mon, 17 Oct 2016 12:37:58 GMT

     [ https://issues.apache.org/jira/browse/SOLR-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexandre Rafalovitch closed SOLR-6769.
---------------------------------------
    Resolution: Cannot Reproduce

> Election bug
> ------------
>
>                 Key: SOLR-6769
>                 URL: https://issues.apache.org/jira/browse/SOLR-6769
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Alexander S.
>         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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message