Collection acquisitions have no enforcement of snapshot stability

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2024-08-05, CAR Team 2024-08-19, CAR Team 2024-09-02, CAR Team 2024-09-16, CAR Team 2024-09-30, CAR Team 2024-10-14, CAR Team 2024-10-28, CAR Team 2024-11-11, CAR Team 2024-11-25, CAR Team 2024-12-23, CAR Team 2025-01-06, CAR Team 2025-01-20, CAR Team 2025-02-03, CAR Team 2025-02-17
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Closing a storage engine snapshot via abandonSnapshot() and WriteUnitOfWork::commit() invalidates the CollectionCatalog snapshot held by callers. There are no preventative measures to ensure that callers do not continue using a potentially invalid catalog snapshot, and this is dangerous.

      This causes memory errors and segfaults like this one: SERVER-81331.

      This is also likely a problem just for Lock-free-reads operations

              Assignee:
              Jordi Olivares Provencio
              Reporter:
              Louis Williams
              Votes:
              0 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: