Stop async updates to the oplogTruncateAfterPoint during primary server shutdown prior to clearing the oplogTruncateAfterPoint

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.4.0-rc0, 4.7.0
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Execution Team 2020-03-23, Execution Team 2020-04-06
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      On replication stepdown we clear the stop the async updates to the oplogTruncateAfterPoint and then null the value here. On shutdown while primary, we clear the oplogTruncateAfterPoint here. However, we do not stop the async updates to the oplogTruncateAfterPoint on primary shutdown, so the async thread can set the oplogTruncateAfterPoint again before shutdown completes.

            Assignee:
            Dianna Hohensee (Inactive)
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: