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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.0-rc0, 4.7.0
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Execution Team 2020-03-23, Execution Team 2020-04-06
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dianna.hohensee Dianna Hohensee
              Reporter:
              dianna.hohensee Dianna Hohensee
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: