lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (SOLR-5593) shard leader loss due to ZK session expiry
Date Tue, 12 Jan 2016 19:14:39 GMT


ASF GitHub Bot commented on SOLR-5593:

Github user cpoerschke closed the pull request at:

> shard leader loss due to ZK session expiry
> ------------------------------------------
>                 Key: SOLR-5593
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>            Reporter: Christine Poerschke
>            Assignee: Mark Miller
>             Fix For: 4.7, Trunk
>         Attachments: CoreAdminHandler.patch
> The problem we saw was that the shard leader ceased to be shard leader (in our case due
to its zookeeper session expiring). The followers thus rejected update requests (DistributedUpdateProcessor
setupRequest's call to ZkStateReader getLeaderRetry) and the leader asked them to recover
(DistributedUpdateProcessor doFinish). The followers published themselves as recovering (CoreAdminHandler
handleRequestRecoveryAction) and the shard leader loss triggered an election in which none
of the followers became the leader due to their recovering state (ShardLeaderElectionContext
shouldIBeLeader). The former shard leader also did not become shard leader because its new
seq number placed it after the existing replicas (LeaderElector checkIfIamLeader seq <=

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message