lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cao Manh Dat (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-12051) Election timeout when no replicas are qualified to become leader
Date Fri, 09 Mar 2018 10:57:00 GMT

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

Cao Manh Dat updated SOLR-12051:
--------------------------------
    Issue Type: Sub-task  (was: Improvement)
        Parent: SOLR-12011

> 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
>         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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message