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

Default shutdown command's 'timeoutSecs' argument to 10 seconds

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.12, 3.4.2, 3.5.2
    • Component/s: Replication
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.4, v3.2
    • Sprint:
      Repl 2016-12-12, Repl 2017-01-23

      Description

      When the shutdown command is run against the primary of a replica set, it first tries to step down. The shutdown command takes a 'timeoutSecs' argument to control how long it waits for secondaries to catch up after it has blocked new writes before it aborts the stepdown and shutdown attempt. This argument, however, defaults to 0, so unless a majority of secondaries are fully caught up to the primary at the moment that the shutdown command is issued then it will fail - which if there are a steady stream of writes happening will likely always be the case. The replSetStepDown command has similar behavior, but its equivalent argument - 'secondaryCatchUpPeriodSecs' - defaults to 10 seconds. We should change shutdown to match the behavior of stepdown so that it's actually possible to use the default behavior to shut down a primary while it is taking writes.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: