Config oplog commitment wait must retrieve optime under replication mutex

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.4.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Repl 2020-03-09
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When we retrieve the configOplogCommitmentOpTime here, we do not hold the ReplicationCoordinator mutex. We must acquire the mutex to call into TopologyCoordinator safely.

              Assignee:
              Pavithra Vetriselvan
              Reporter:
              Will Schultz
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: