[SERVER-60592] DDL participant commands need to ensure they make a write with their txnNumber - MongoDB Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: 5.0.2, 5.1.0-rc1
Fix Version/s: 5.2.0, 5.0.4, 5.1.0-rc2
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v5.1, v5.0
Sprint:
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

related to

SERVER-56648 Make dropCollection resilient to network partitions

Closed

SERVER-56649 Make renameCollection resilient to network partitions

Closed

SERVER-56650 Make createCollection resilient to network partitions

Closed

Activity

People

Assignee:: Jordi Serra Torrens

Reporter:: Jordi Serra Torrens

Participants:: Githook User, Jordi Serra Torrens

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: Oct 11 2021 11:31:41 AM UTC

Updated:: Oct 21 2021 06:00:30 PM UTC

Resolved:: Oct 18 2021 02:52:02 PM UTC