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

Consider allowing any node to become leader, regardless of their last published state.



    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.3, 8.0
    • Component/s: SolrCloud
    • Labels:


      Now that we allow a min replication param for updates, I think it's time to loosen this up. Currently, you can end up in a state where no one in a shard thinks they can be leader and you so do this fast ugly infinite loop trying to pick the leader.

      We should let anyone that is able to properly sync with the available replicas to become leader if that process succeeds.

      The previous strategy was to account for the case of not having enough replicas after a machine loss to ensure you don't lose the data. The idea was that you should stop the cluster to avoid losing data and repair and get all your replicas involved in a leadership election. Instead, we should favor carrying on, and those that want to ensure they don't lose data due to major replica loss should use the min replication update param.


        1. SOLR-7034.patch
          9 kB
          Cao Manh Dat
        2. SOLR-7034.patch
          52 kB
          Cao Manh Dat
        3. SOLR-7034.patch
          49 kB
          Cao Manh Dat

          Issue Links



              • Assignee:
                caomanhdat Cao Manh Dat
                markrmiller@gmail.com Mark Miller
              • Votes:
                0 Vote for this issue
                10 Start watching this issue


                • Created: