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

Ban reads with readConcern snapshot on pre-images and change collection tables

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • Execution EMEA Team 2023-08-21, Execution EMEA Team 2023-09-04

      Pre-images and change collection tables prune old content using untimestamped truncates. A read establishing a snapshot at a point in time (PIT) may see data inconsistent with that PIT: data that should have been present at that PIT will be missing if it was truncated, since a non-truncated operation effectively overwrites history.

      This behaviour is similar to capped collections before they replicated deletes explicitly (i.e. before SERVER-16049); we similarly banned reads with snapshot read concern on those (see SERVER-47574 and SERVER-47824).

            Assignee:
            miquel.munoz@mongodb.com Miquel Munoz (Inactive)
            Reporter:
            josef.ahmad@mongodb.com Josef Ahmad
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: