[SERVER-42830] Applying a rename operation can result in multiple WT transactions Created: 15/Aug/19 Updated: 29/Oct/23 Resolved: 21/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, 4.2.4 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||||||
| Sprint: | Execution Team 2019-08-26 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When renaming a collection via an oplog entry, it's possible to hit this clause. That statement performs work in its own WUOW/transaction and commits separately to completing the rename. Note this logic is not a bug in the sense that it would only manifest if crashing/restarting during initial sync were smarter than retrying from the beginning. However, this splitting of transactions results in an untimestamped write on the catalog. Verifying that all (necessary) writes to the catalog are timestamped is easier if that's also true during initial sync. The motivation for this ticket is to add timestamp verification. |
| Comments |
| Comment by Githook User [ 19/Feb/20 ] |
|
Author: {'name': 'Daniel Gottlieb', 'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: (cherry picked from commit 10dd7ef95fab6b869818f54827d4e03924846432) |
| Comment by Githook User [ 21/Aug/19 ] |
|
Author: {'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'name': 'Daniel Gottlieb'}Message: |