Remove DB X lock acquisition for secondary index builds

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.2.0-rc1, 4.3.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Execution Team 2019-06-03, Execution Team 2019-06-17
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The IndexBuildsCoordinator, which builds background indexes on secondaries, still takes a Database X lock, despite changes made on primaries to take a Collection X lock.

      Secondaries should take the same locks as primaries, which could otherwise lead to unexpected deadlocks.

              Assignee:
              Gregory Wlodarek
              Reporter:
              Louis Williams
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: