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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.4
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Execution Team 2020-02-24, Execution Team 2020-03-09
    • Linked BF Score:
      50

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: