Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-60592

DDL participant commands need to ensure they make a write with their txnNumber

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 5.0.2, 5.1.0-rc1
    • 5.2.0, 5.0.4, 5.1.0-rc2
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v5.1, v5.0
    • Sharding EMEA 2021-11-01

    Description

      Similarly to the dummy write we do at the end of _configsvrRemoveTags (and _configsvrRemoveTags and _configsvrRenameCollectionMetadata) in order to ensure that an oplog entry is written with the txnNumber of the "retryable write" _configsvrRemoveTags was ran on, we need to do the same with the following commands:

      _shardsvrCreateCollectionParticipant
      _shardsvrDropCollectionParticipant
      _shardsvrRenameCollectionParticipant
      _shardsvrRenameCollectionParticipantUnblock

      This is because those commands may not have written anything on the oplog that durably stores that txnNumber.

      Attachments

        Issue Links

          Activity

            People

              jordi.serra-torrens@mongodb.com Jordi Serra Torrens
              jordi.serra-torrens@mongodb.com Jordi Serra Torrens
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: