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

Don't enforce data freshness for step-up command

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.2, 3.5.2
    • Component/s: Replication
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4
    • Sprint:
      Repl 2017-01-23
    • Linked BF Score:
      0

      Description

      We don't run priority takeover if the node is not within 2 seconds with the most up-to-date member. This behavior affects step-up command as well. We should skip the check for step-up command.

        Attachments

          Issue Links

          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-27148 StepUp command should take over primary even if repl lagged

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-26748 Don't call for priority takeover when repl lagged

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-27461 Retry connecting to shut down primary until failure in shutdown_primary.js

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: