[
https://issues.apache.org/jira/browse/SOLR-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238693#comment-14238693
]
Anshum Gupta commented on SOLR-6769:
------------------------------------
[~aheaven] I would recommend you to post such issues on the user-list before
creating a JIRA. This would come in handy:
https://wiki.apache.org/solr/UsingMailingLists
Though I think it's not really an issue, I'm not closing this issue for now.
However, I'll reduce the Priority on this one primarily due to lack of
information on the issue.
* What version of Solr were you running?
* What version of Java? Web server?
* How were you running it? External ZK?
* What do you mean by "stopped normally"? Shard is a logical entity, replica is
a physical one. Do you mean you stopped the leader of Shard1?
* What did you expect should have happened?
..
> Election bug
> ------------
>
> Key: SOLR-6769
> URL: https://issues.apache.org/jira/browse/SOLR-6769
> Project: Solr
> Issue Type: Bug
> Reporter: Alexander S.
> Priority: Critical
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
