[SERVER-60592] DDL participant commands need to ensure they make a write with their txnNumber Created: 11/Oct/21 Updated: 29/Oct/23 Resolved: 18/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 5.0.2, 5.1.0-rc1 |
| Fix Version/s: | 5.2.0, 5.0.4, 5.1.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v5.1, v5.0
|
||||||||||||||||||||
| Sprint: | Sharding EMEA 2021-11-01 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| 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 This is because those commands may not have written anything on the oplog that durably stores that txnNumber. |
| Comments |
| Comment by Githook User [ 19/Oct/21 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: (cherry picked from commit c83185229c960f321d2eb121ff6a4e8a043dd124) |
| Comment by Githook User [ 19/Oct/21 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: (cherry picked from commit c83185229c960f321d2eb121ff6a4e8a043dd124) |
| Comment by Githook User [ 18/Oct/21 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |