91 — ShutdownInProgress

replicationconnectivity

The server is shutting down and cannot accept new operations

What is happening?

ShutdownInProgress indicates that the mongod or mongos process has begun its shutdown sequence and is rejecting new operations. In-flight operations may also be interrupted with this error. This is expected during planned maintenance, rolling restarts, or Atlas scaling events.

Common causes

  1. Planned server maintenance or restart initiated by an administrator
  2. Atlas scaling event or maintenance window
  3. Kubernetes pod eviction or rescheduling
  4. Server process received SIGTERM or SIGINT
  5. Rolling restart of replica set members during an upgrade

Source code references

ErrorCodes::ShutdownInProgress found in 137 locations in the MongoDB server source.

Diagnostic Steps

Related Issues

SERVER-135154Closed
Enforce the PinnedConnectionTaskExecutor lifetime contract during mongot shutdown
h3. Context Make mongod shutdown honor the PinnedConnectionTaskExecutor (PCTE) lifetime contract, so a $search cursor created during shutdown cannot outlive its underlying mongot task executor. This closes the invariant failure tracked by AF-21589 (same class as AF-4442 / SERVER-108562). h3. Scope # Gate new mongot cursor creation: once search-executor shutdown begins, cursor acquisition fails fast with ShutdownInProgress (convention already documented in search_task_executors.h) so no new PC
NODE-7859Backlog
RTTPinger never reschedules after a failed ping, leaving latestRtt frozen at a stale value
h3. Use Case h3. Expected Behavior After a mongos restart, the latency measurement on a server connection should be updated at regular intervals as it was before the restart. h3. Actual Behavior and Impact During a rolling mongos restart, a server node enters quiesce mode and answers the RTT pinger's hello with {{{}ShutdownInProgress{}}}. {{{}RTTPinger.measureRoundTripTime{}}}'s onrejected callback destroys the connection, sets it to undefined, and returns without setting another {{me
JAVA-5125Backlog
Some write concern errors are not retried according to spec
JAVA-5124 was opened because the legacy retryable writes test suite was not being run against sharded clusters. After that issue was addressed it was observed that tests of write concern error retryability fail on 4.2 and 4.4 sharded clusters. The tests that fail mostly have description ending with "succeeds after WriteConcernError ShutdownInProgress", although there are a few other failures as well. While attempting to debug these test failures, the following observations were made: 1.