Allow untimestamped writes for the entirety of initial sync retry

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.0.0-rc0, 6.3.2
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v6.3
    • Execution Team 2023-02-20, Execution Team 2023-03-06, Execution Team 2023-03-20
    • 151
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Fausto Leyva (Inactive)
              Reporter:
              Fausto Leyva (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: