[SERVER-76985] New commit phase of sharded renameCollection is not idempotent Created: 10/May/23 Updated: 29/Oct/23 Resolved: 11/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 7.0.0-rc0, 7.1.0-rc0 |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Sergi Mateo Bellido |
| 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: |
v7.0
|
||||||||||||||||
| Sprint: | Sharding EMEA 2023-05-15 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 148 | ||||||||||||||||
| Description |
|
The commit phase of the renameCollection has been recently modified to perform the metadata changes as a multi document TXN. However, this TXN has one stmt that is not idempotent, so if the whole commit phase is re-executed due to any random failure it will end up failing and being retried forever. |
| Comments |
| Comment by Githook User [ 12/May/23 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: (cherry picked from commit dc864de3212e83b2d2a7553b6d9a975c523305e6) |
| Comment by Githook User [ 11/May/23 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |