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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.4.0-rc0, 4.7.0
    • None
    • Storage
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Execution Team 2020-03-23, Execution Team 2020-04-06
    • 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

        Activity

          People

            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: