[SERVER-82628] Avoid updates to PreImageTruncateMarkers before inserts are committed Created: 31/Oct/23 Updated: 13/Nov/23 Resolved: 09/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | CAR Team 2023-11-13 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 120 | ||||||||
| Description |
|
In the pre-images truncate marker initialization code, we call _truncateManager.updateMarkersOnInsert outside of an onCommit() handler. This means that a placeholder for truncate markers on a given nsUUID can be created for an empty collection before any inserts are committed/ visible. In general, updating the in-memory truncate marker structures outside of onCommit() handlers can lead to unexpected behavior. |
| Comments |
| Comment by Githook User [ 09/Nov/23 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |