Available since: 1.0.0
Time complexity: O(N) when saving, where N is the total number of keys in all databases when saving data, otherwise O(1)
The command behavior is the following:
CLIENT PAUSEwith the
shutdown-timeout(default 10 seconds) for replicas to catch up the replication offset.
If persistence is enabled this commands makes sure that Redis is switched off without any data loss.
Note: A Redis instance that is configured for not persisting on disk (no AOF
configured, nor "save" directive) will not dump the RDB file on
usually you don't want Redis instances used only for caching to block on when
Also note: If Redis receives one of the signals
SIGINT, the same shutdown sequence is performed.
See also Signal Handling.
It is possible to specify optional modifiers to alter the behavior of the command. Specifically:
When a save point is configured or the SAVE modifier is specified, the shutdown may fail if the RDB file can't be saved. Then, the server continues to run in order to ensure no data loss. This may be bypassed using the FORCE modifier, causing the server to exit anyway.
When the Append Only File is enabled the shutdown may fail because the system is in a state that does not allow to safely immediately persist on disk.
Normally if there is an AOF child process performing an AOF rewrite, Redis will simply kill it and exit. However, there are situations where it is unsafe to do so and, unless the FORCE modifier is specified, the SHUTDOWN command will be refused with an error instead. This happens in the following situations:
There are situations when we want just to terminate a Redis instance ASAP, regardless of what its content is. In such a case, the command SHUTDOWN NOW NOSAVE FORCE can be used. In versions before 7.0, where the NOW and FORCE flags are not available, the right combination of commands is to send a CONFIG appendonly no followed by a SHUTDOWN NOSAVE. The first command will turn off the AOF if needed, and will terminate the AOF rewriting child if there is one active. The second command will not have any problem to execute since the AOF is no longer enabled.
Since Redis 7.0, the server waits for lagging replicas up to a configurable
shutdown-timeout, by default 10 seconds, before shutting down.
This provides a best effort minimizing the risk of data loss in a situation where no save points are configured and AOF is disabled.
Before version 7.0, shutting down a heavily loaded master node in a diskless setup was more likely to result in data loss.
To minimize the risk of data loss in such setups, it's advised to trigger a manual
CLUSTER FAILOVER) to demote the master to a replica and promote one of the replicas to be the new master, before shutting down a master node.
Simple string reply:
ABORT was specified and shutdown was aborted.
On successful shutdown, nothing is returned since the server quits and the connection is closed.
On failure, an error is returned.
>= 7.0.0: Introduced waiting for lagging replicas before exiting.