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

Config oplog commitment wait must retrieve optime under replication mutex

XMLWordPrintableJSON

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

      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@mongodb.com Pavithra Vetriselvan
            Reporter:
            william.schultz@mongodb.com Will Schultz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: