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

on stepdown/election, SECONDARY should consume all available oplog

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • Replication
    • None
    • ALL

    Description

      If the user performs a stepDown on an otherwise healthy PRIMARY and the SECONDARY has N seconds of lag, then that N seconds of activity is lost. If the PRIMARY is otherwise OK, then the SECONDARY should try to consume all possible oplog while the election takes place (no activity to cluster during this time).

      This allows users to call stepDown on busy sets that may always have lag and ensure they aren't dropping data on the floor when they don't need to.

      Attachments

        Issue Links

          Activity

            People

              milkie@mongodb.com Eric Milkie
              kennygorman Kenny Gorman
              Votes:
              8 Vote for this issue
              Watchers:
              21 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: