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

Signaling 1-node replica set to shut down now takes an extra 10 seconds

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Service Arch
    • ALL
    • Service Arch 2019-03-25

      It seems like attempting to run ReplicationCoordinator::stepDown() is unnecessary when the replica set configuration is known to only contain one node electable as primary. The extra time it takes to shut down the replica set is mildly annoying for certain aspects of my local development workflow.

      2019-03-21T03:09:22.009-0400 I  CONTROL  [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
2019-03-21T03:09:22.009-0400 I  REPL     [RstlKillOpthread] Starting to kill user operations
2019-03-21T03:09:22.009-0400 I  REPL     [RstlKillOpthread] Stopped killing user operations
2019-03-21T03:09:32.020-0400 I  REPL     [RstlKillOpthread] Starting to kill user operations
2019-03-21T03:09:32.020-0400 I  REPL     [RstlKillOpthread] Stopped killing user operations
2019-03-21T03:09:32.020-0400 I  STORAGE  [signalProcessingThread] Failed to stepDown in non-command initiated shutdown path ExceededTimeLimit: No electable secondaries caught up as of 2019-03-21T03:09:32.020-0400. Please use the replSetStepDown command with the argument {force: true} to force node to step down.
2019-03-21T03:09:32.020-0400 I  NETWORK  [signalProcessingThread] shutdown: going to close listening sockets...

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: