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

Accessing multiple collections in an operation on a secondary can crash

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Minor Change
    • ALL
    • Execution Team 2019-11-04, Execution Team 2019-11-18, Execution Team 2019-12-02
    • 10

      This is one of those "pick two of the three properties" except it's pick "X of the Y properties" for unknown values of X and Y.
      The properties:

      • Allow lazy accessing of collections (i.e: not known ahead of time) after acquiring a storage engine snapshot.
      • Have instances of ghost timestamping catalog operations.
      • Not maintaining a versioned catalog.
      • Reacquire snapshots with different locks on a catalog conflict.
      • Ensure user operations don't fail due to a catalog conflicts.

      It might be easiest to uassert when an operation cannot easily get a snapshot that is allowed to read from all necessary collections.

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: