DDL participant commands should ensure they are ran within a session after 6.0 branches out

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding EMEA 2022-06-13, Sharding EMEA 2022-06-27
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      On 5.0.2, it was made that the following commands are ran with a sessionId & txnNumber attached:
      _shardsvrCreateCollectionParticipant
      _shardsvrDropCollectionParticipant
      _shardsvrRenameCollectionParticipant
      _shardsvrRenameCollectionParticipantUnblock

      However, 5.0.0 binaries did not attach it yet. So for backwards compatibility, those commands do not enforce that they are run as a "retryable write". After 6.0 branches out, we will be guaranteed that no more binaries that do not attach the sessionId are in the cluster. This ticket is to enforce that those commands are run with sessionId & txnNumber

            Assignee:
            Jordi Serra Torrens
            Reporter:
            Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: