Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-80538

New refine collection shard key might resume migrations on unretriable errors

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0, 7.1.0-rc2
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v7.1
    • Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18

      SERVER-76486 added a resume migrations call in the onCompletion callback, however, if there is a non-retriable error in a phase greater than kRemoteIndexValidation the migrations will be resumed when they shouldn't, because we have the forward progress until success guarantee. However, kRemoteIndexValidation is a validation phase that must happen without any migrations, and an error might be thrown in case we find some shard that does not have the index created, so, we should ensure that we resume migrations of the onCompletion callback only happens on non-retriable error in the kRemoteIndexValidation phase.

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: