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

Collection isolation should work in SideTransaction

    • Type: Icon: Task Task
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution

      The Collection isolation implemented for lock free reads that resides inside the CollectionCatalog is implemented as a decoration on the OperationContext. This leads to SideTransaction's to observe uncommitted state from their parent.

      Multikey is set inside a SideTransaction and need to operate directly on the DurableCatalog because it cannot trust the metadata in the Collection because of this.

      The isolation should be implemented either like UncommittedCollections where the TransactionParticipant can detach/attach the state. Or as a decoration on the RecoveryUnit.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            henrik.edin@mongodb.com Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: