• Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 4.10.4, 5.5.2, 6.1, 6.2
    • Fix Version/s: 6.2.1, 6.3, 7.0
    • Component/s: SolrCloud
    • Security Level: Public (Default Security Level. Issues are Public)


      Solr’s shard split can lose documents if the parent/sub-shard leader is killed (or crashes) between the time that the new sub-shard replica is created and before it recovers. In such a case the slice has already been set to ‘recovery’ state, the sub-shard replica comes up, finds that no other replica is up, waits until the leader vote wait time and then proceeds to become the leader as well as publish itself as active. If the former leader node comes back online, the overseer seeing that all replicas of the sub-shard are now ‘active’, sets the parent slice as ‘inactive’ and the new sub-shard as ‘active’.


        1. SOLR-9438.patch
          27 kB
          Shalin Shekhar Mangar
        2. SOLR-9438.patch
          26 kB
          Shalin Shekhar Mangar
        3. SOLR-9438.patch
          22 kB
          Shalin Shekhar Mangar
        4. SOLR-9438.patch
          21 kB
          Shalin Shekhar Mangar
        5. SOLR-9438.patch
          9 kB
          Shalin Shekhar Mangar
        6. SOLR-9438.patch
          9 kB
          Shalin Shekhar Mangar
        7. SOLR-9438-false-replication.log
          1007 kB
          Shalin Shekhar Mangar
        8. SOLR-9438-split-data-loss.log
          1.00 MB
          Shalin Shekhar Mangar

          Issue Links



              • Assignee:
                shalinmangar Shalin Shekhar Mangar
                shalinmangar Shalin Shekhar Mangar
              • Votes:
                0 Vote for this issue
                4 Start watching this issue


                • Created: