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

Clarify and correct synchronization of isOplogTruncateAfterPointBeingUsedForPrimary

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0, 4.4.5
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v4.4
    • Execution Team 2020-08-24, Execution Team 2020-09-07
    • 8

      The variable _isPrimary in replication_consistency_markers_impl.cpp is used to signal whether or not to write out the oplog truncation point during journal flushing. However, it is not synchronized with the actual write to the truncation point. The code which clears it attempts to work around this by interrupting and waiting for the journal flusher, but the journal flusher is not safely interruptible at this point.

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: