Ensure that resharding donor majority commits its state before acknowledging coordinator commands

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ALL
    • ClusterScalability 22Jun-6Jul
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Resharding recipients always ensure that it's persisted state is majority committed before setting the promise the coordinator commands would wait for. This doesn't appear to be the case for donors.

      This can potentially create a scenario where a donor steps up with a new primary without the newly persisted state and gets stuck waiting for the coordinator to send the command to advance it, but the coordinator has already moved ahead and won't send the command again (until a another coordinator steps up and possibly resets the internal state).

            Assignee:
            Abdul Qadeer
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: