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

ReplicationCoordinatorImpl::_requestRemotePrimaryStepdown doesn't work

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.13, 3.3.8
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.2
    • Sprint:
      Repl 13 (04/22/16), Repl 14 (05/13/16), Repl 15 (06/03/16)

      Description

      This generates a stepdown command which fails:

      { ok: 0.0, errmsg: "stepdown period must be longer than secondaryCatchUpPeriodSecs", code: 2 }
      

      This is called by a member with a higher priority that is not currently the primary so it can have a change to do a priority takeover, and to be elected. The fact that this is currently broken doesn't affect the system because the primary will also step-down on its own when it sees a higher priority member that can be elected. Fixing this might improve the timeliness of the step-down and forthcoming election.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: