Add command for resharding coordinator to notify recipients that critical section has started

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ClusterScalability Nov10-Nov24
    • 5
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is needed by SERVER-109322.

      On a recipient shard that skips cloning and applying, currently it transitions straight from "cloning" to "applying" to "strict-consistency". If the recipient is not a donor, the transition to “strict-consistency” involves acquiring the critical section to prepare for collection renaming (SERVER-53653). So this unexpectedly leads to early critical section on the primary shard, which can cause misrouted writes to get blocked long before the critical section is officially engaged by the coordinator when resharding is about to commit.

      To avoid this, such a recipient should wait for the critical section to start before transitioning to "strict-consistency". The goal for this ticket is to add a command for the coordinator to notify recipients that critical section has started.

            Assignee:
            Cheahuychou Mao
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: