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

Collection acquisitions have no enforcement of snapshot stability

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • ALL
    • CAR Team 2024-08-05, CAR Team 2024-08-19, CAR Team 2024-09-02, CAR Team 2024-09-16

      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@mongodb.com Jordi Olivares Provencio
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: