Allow TransactionParticipant to "restart" from state::kNone in order to upgrade retryable write to transaction

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.10
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2019-03-25, Sharding 2019-04-08
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In order to allow updating a document's shard key value when the write is not part of a multi-stmt transaction, the TransactionParticipant state machine needs to be allowed to restart from state::kNone. This is so that we can re-use the session and transaction number for both the original update and the internal transaction started by MongoS.

            Assignee:
            Blake Oler
            Reporter:
            Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: