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

Rolling back a partially-committed collection creation transaction can cause catalog inconsistencies

    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:
      48

      Description

      This scenario can cause catalog inconsistencies.

      Transaction 1 creates collection B
      Transaction 2 creates collection A
      Transaction 2 commits
      Transaction 1 creates collection A
      Transaction 1 attempts to commit, and fails due to conflicting creation of "A".

      The catalog inconsistency results because as we apply the commit of transaction 1, we register collection B in the catalog before finding out that collection A failed to be registered. We do not currently have rollback handling to roll back the registration of collection B.

        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:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: