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

Bugs in MoveReplicaCmd handling of failures

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 7.0, 7.0.1, 7.1, 8.0
    • Fix Version/s: 7.2, 8.0
    • Component/s: None
    • Labels:
      None

      Description

      Spin-off from SOLR-11449:

      There's a section of code in moveNormalReplica that ensures that we don't lose a shard leader during move. There's no corresponding protection in moveHdfsReplica, which means that moving a replica that is also a shard leader may potentially lead to data loss (eg. when replicationFactor=1).
      Also, there's no rollback strategy when moveHdfsReplica partially fails, unlike in moveNormalReplica where the code simply skips deleting the original replica - it seems that the code should attempt to restore the original replica in this case? When RF=1 and such failure occurs then not restoring the original replica means lost shard.

        Attachments

        1. SOLR-11458.diff
          45 kB
          Andrzej Bialecki
        2. SOLR-11458.diff
          46 kB
          Andrzej Bialecki

          Issue Links

            Activity

              People

              • Assignee:
                ab Andrzej Bialecki
                Reporter:
                ab Andrzej Bialecki
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: