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

Audit internal usage of list databases or collections for needing snapshot consistency

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2024-07-08, CAR Team 2024-07-22, CAR Team 2024-08-05

      SERVER-90893 is changing the list databases command to be consistent with a storage snapshot. SERVER-82221 similarly made the changes to list collections. Both commands now have an associated storage snapshot, and they consider the collections marked pending commit. If the storage snapshot says that the transaction related to collection creation has been committed, these commands consider the collections for the list. Note: Collection pending drops are not taken into account.

      The collection catalog offers ways to lookup these lists, considering or ignoring the storage snapshot. There are places in the code where we directly access catalog routines that do not consider a storage snapshot. We should audit these cases in case they also need a storage snapshot level consistency for correctness.

            Assignee:
            Unassigned Unassigned
            Reporter:
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: