Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-78428

Truncate change stream change collections at startup to avoid recovery holes

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Execution EMEA Team 2023-07-10, Execution EMEA Team 2023-07-24, Execution EMEA Team 2023-09-04, Execution EMEA Team 2023-09-18, Execution EMEA Team 2023-10-02

      During crash recovery untimestamped truncates can spontaneously be partially rolled back due to lack of information at the WiredTiger layer.

      This can cause "holes" to manifest in preimages and change collections where we have patches of missing data that should've expired.

      To avoid these holes we should range truncate the collections at startup so that the expired data is deleted again and the holes are not presented to the end user.

            Assignee:
            haley.connelly@mongodb.com Haley Connelly
            Reporter:
            haley.connelly@mongodb.com Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: