Migration coordinator recovery task should bump the txnNumber on the session used to send _recvChunkStart

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2020-02-10, Sharding 2020-02-24
    • 43
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      While working on SERVER-45339, we re-realized why we originally wanted to make the recovery task bump the txnNumber used to send _recvChunkStart.

      It is to prevent an old donor primary from sending _recvChunkStart after the new donor primary has already completed the recovery, because this would cause a new range deletion task to be written on the recipient that would never get cleaned up.

      This ticket should make the donor persist the lsid and txnNumber used to send _recvChunkStart again, and make the recovery task do a dummy write using the lsid and txnNumber + 1 on the recipient before sending the decision to the recipient.

            Assignee:
            Alexander Taskov (Inactive)
            Reporter:
            Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: