[
https://issues.apache.org/jira/browse/SOLR-12051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393857#comment-16393857
]
ASF subversion and git services commented on SOLR-12051:
--------------------------------------------------------
Commit 05d4a9320cfe95d93655feb39a6c6a2945e98c76 in lucene-solr's branch
refs/heads/master from [~caomanhdat]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=05d4a93 ]
SOLR-12051: Adding error log in case of data loss
> Election timeout when no replicas are qualified to become leader
> ----------------------------------------------------------------
>
> Key: SOLR-12051
> URL: https://issues.apache.org/jira/browse/SOLR-12051
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Priority: Major
> Fix For: 7.3, master (8.0)
>
> Attachments: SOLR-12051.patch
>
>
> After SOLR-12011 get committed, we can lead into the case when no active
> replicas are qualified to become the leader. The only 2 solutions for users
> in this case are
> * Using FORCE_LEADER API
> * Bring back the old leader
> This ticket will introduce a leader election timeout so current active
> replicas can ignore the lost updates and go ahead to become the leader. I
> think it will be better and not confuse users by reusing {{leaderVoteWait}}
> (the current usage of {{leaderVoteWait}} for waiting replicas come up before
> leader election is no longer needed)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
