Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-6763

Shard leader election thread can persist across session expiry


    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.10.4, 5.0
    • Component/s: None
    • Labels:


      A ZK connection loss during a call to ElectionContext.waitForReplicasToComeUp() will result in two leader election processes for the shard running within a single node - the initial election that was waiting, and another spawned by the ReconnectStrategy. After the function returns, the first election will create an ephemeral leader node. The second election will then also attempt to create this node, fail, and try to put itself into recovery. It will also set the 'isLeader' value in its CloudDescriptor to false.

      The first election, meanwhile, is happily maintaining the ephemeral leader node. But any updates that are sent to the shard will cause an exception due to the mismatch between the cloudstate (where this node is the leader) and the local CloudDescriptor leader state.

      I think the fix is straightfoward - the call to zkClient.getChildren() in waitForReplicasToComeUp should be called with 'retryOnReconnect=false', rather than 'true' as it is currently, because once the connection has dropped we're going to launch a new election process anyway.


        1. SOLR-6763.patch
          3 kB
          Alan Woodward
        2. SOLR-6763.patch
          2 kB
          Alan Woodward



            • Assignee:
              romseygeek Alan Woodward
              romseygeek Alan Woodward
            • Votes:
              0 Vote for this issue
              8 Start watching this issue


              • Created: