[SERVER-73887] Allow untimestamped writes for the entirety of initial sync retry Created: 10/Feb/23 Updated: 29/Oct/23 Resolved: 16/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0, 6.3.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Fausto Leyva (Inactive) | Assignee: | Fausto Leyva (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 | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v6.3
|
||||||||
| Sprint: | Execution Team 2023-02-20, Execution Team 2023-03-06, Execution Team 2023-03-20 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 151 | ||||||||
| Description |
|
If we fail InitialSync, we clean up/ reset the catalog before retrying InitialSync. If this occurs, it is safe to allow for untimestamped writes throughout _truncateOplogAndDropReplicatedDatabases. We already allow for untimestamped writes: here. The issue is that this flag gets reset after one WUOW/transaction commits or aborts. Proposed solution: add an RAII type to allow for untimestamped writes over a chunk of code - resilient to being reset upon wuow commit/abort on the same RecoveryUnit. |
| Comments |
| Comment by Githook User [ 20/Apr/23 ] |
|
Author: {'name': 'Faustoleyva54', 'email': 'fausto.leyva@mongodb.com', 'username': 'Faustoleyva54'}Message: |
| Comment by Githook User [ 16/Mar/23 ] |
|
Author: {'name': 'Faustoleyva54', 'email': 'fausto.leyva@mongodb.com', 'username': 'Faustoleyva54'}Message: |