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.
- related to
-
SERVER-56648 Make dropCollection resilient to network partitions
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-