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

Collections should not be visible in CollectionCatalog lookups until storage transaction commit

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2020-02-24, Execution Team 2020-03-09
    • 50

      Presently, collections created inside multi-document transactions are each individually registered during transaction commit. However, if the transaction gets aborted midway through the commit, those previously registered collections need to be rolled back.

      In order to guarantee transaction isolation, the newly-registered collections should only be visible once the entire transaction has committed.

      One potential solution to achieve this visibility handling is by preventing reads on the existing minVisibleTimestamp.

            Assignee:
            maria.vankeulen@mongodb.com Maria van Keulen
            Reporter:
            maria.vankeulen@mongodb.com Maria van Keulen
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: