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

Clarify and correct synchronization of isOplogTruncateAfterPointBeingUsedForPrimary

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0, 4.4.5
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Execution Team 2020-08-24, Execution Team 2020-09-07
    • Linked BF Score:
      8

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dianna.hohensee Dianna Hohensee
              Reporter:
              matthew.russotto Matthew Russotto
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: