Reset the original user write blocking state on replicasets after fail during addShardCoordinator

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-03-03, CAR Team 2025-03-17, CAR Team 2025-03-31
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The checkShardPrecondition phase of addShard before we check the replicaset cleanness we block user writes and if the replicaset had any data, then we unblock the user writes and fail. this is not 100% safe as the RS might had user write blocking already before we set it up, and in this case a failing addshard practically just unlocks the RS.

      the idea is to store the original blocking phase in the add shard coordinator document and use that data on failure.

            Assignee:
            Anna Maria Nestorov
            Reporter:
            Wolfee Farkas
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: