SHUTDOWN

Synchronously saves the database(s) to disk and shuts down the Redis server.

Browse all commands · Upstream source documentation

Reference field	Value
Canonical name	SHUTDOWN
Catalog group	Server commands
Upstream since	1.0.0 — upstream Redis/module version, not an ffkv release
Pinned catalog	Redis 8.10.0

Syntax

SHUTDOWN [NOSAVE | SAVE] [NOW] [FORCE] [ABORT]

ffkv behavior and limits

Server introspection describes ffkv, not a Redis process. MEMORY reports owned-allocation estimates, not jemalloc accounting. Administrative changes can affect all clients or persistent data; consult the scenario and operations guide before using destructive forms.

Source: README.md:393–395, 601–642; tests/bdd/features/server.feature; tests/bdd/features/catalog.feature.

Data-changing administration: use an isolated dataset or a verified backup. Lost replies have an unknown outcome; never blindly replay a destructive operation.

All requests share the 8 MiB framing/1,024-argument ingress limit; normal RESP replies have 64 MiB wire/logical budgets with bounded nesting/value counts. Management and Lua origins impose smaller budgets. These are not a process RSS cap. Catalog inclusion is not exhaustive option or wire-format parity. See limits and compatibility.

Upstream metadata

The following fields come from the pinned Redis metadata, not measured ffkv performance or an assertion that ffkv enforces every upstream flag. Running COMMAND INFO/COMMAND DOCS describe the current engine.

Upstream Redis complexity: O(N) when saving, where N is the total number of keys in all databases when saving data, otherwise O(1)

Upstream arity: -1 (includes the command name; a negative number is a minimum).

Command flags: ADMIN, NOSCRIPT, LOADING, STALE, NO_MULTI, SENTINEL, ALLOW_BUSY.

Argument structure

Argument	Type	Constraints / metadata
save-selector	oneof	optional
↳ nosave	pure-token	token: NOSAVE
↳ save	pure-token	token: SAVE
now	pure-token	optional; token: NOW; since: 7.0.0
force	pure-token	optional; token: FORCE; since: 7.0.0
abort	pure-token	optional; token: ABORT; since: 7.0.0

Additional pinned upstream metadata

{
  "group": "server",
  "since": "1.0.0",
  "history": [
    [
      "7.0.0",
      "Added the `NOW`, `FORCE` and `ABORT` modifiers."
    ]
  ]
}

Metadata source · Local snapshot: src/command_metadata.json, key shutdown.

BDD coverage and source examples

These are source observations, not a test run performed by this documentation build. A tag identifies scenario intent; an extracted vector identifies a command invocation, which may intentionally produce an error. Scenarios may require setup, multiple connections, persistence, cluster nodes or native-module fixtures.

• Saved shutdown exits and persists the dataset — tests/bdd/features/server.feature:511; command tag.
• Graceful shutdown drains a save and its scheduled successor from EXEC — tests/bdd/features/transactions_runtime.feature:185; command tag.

Scenario tags are present, but no safely parsed JSON command vector was extracted. Consult the named feature source for fixture-driven or parameterized execution; no executable example is invented here.