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

Clear the oplogTruncateAfterPoint timestamp on stepdown

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Execution Team 2019-06-17, Execution Team 2019-07-01, Execution Team 2019-07-29, Execution Team 2019-08-12, Execution Team 2019-11-04, Execution Team 2019-11-18

      We will be setting the oplogTruncateAfterPoint continuously in mode PRIMARY so that we can safely replicate before journaling. SERVER-41389 will pause the thread that sets the oplogTruncateAfterPoint in mode SECONDARY, but we are not guaranteed to run batch application, which unsets the oplogTruncateAfterPoint, before potentially stepping up to primary again.

      UPDATE: we are pivoting to unsetting the value on stepdown, as opposed to removing the invariant on stepup.

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

              Created:
              Updated:
              Resolved: