Donor starts shard split operation in kBlocking

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Server Serverless 2022-03-21
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Today we start a shard split operation with either a kUninitialized or kAborted state written to the durable state document, which can be problematic because a stepdown between initial state document insertion and transition to the first state (kBlocking) will result in trying to re-insert the state document when a secondary steps up. We should never write kUninitialized to disk, and instead make transition to kBlocking the first write (if not aborted).

            Assignee:
            Didier Nadeau
            Reporter:
            Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: