CLUSTER COUNT-FAILURE-REPORTS

Returns the number of active failure reports active for a node.

Browse all commands · Upstream source documentation

Reference field	Value
Canonical name	CLUSTER COUNT-FAILURE-REPORTS
Catalog group	Cluster commands
Upstream since	3.0.0 — upstream Redis/module version, not an ffkv release
Pinned catalog	Redis 8.10.0

Syntax

CLUSTER COUNT-FAILURE-REPORTS node-id

ffkv behavior and limits

Requires —cluster-enabled. Hash slots, MOVED/ASK, membership, migration and failover use ffkv’s authenticated peer bus, not the Redis cluster bus. Do not attempt to join a Redis cluster. Tested behavior is not production-HA certification.

Source: README.md:625–642; tests/bdd/features/cluster.feature.

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) where N is the number of failure reports

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

Command flags: ADMIN, LOADING, STALE.

Command tips: NONDETERMINISTIC_OUTPUT.

Argument structure

Argument	Type	Constraints / metadata
node-id	string	Required

Additional pinned upstream metadata

{
  "group": "cluster",
  "since": "3.0.0"
}

Metadata source · Local snapshot: src/command_metadata.json, key cluster|count-failure-reports.

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.

• Automatic election retains acknowledged data when the first voting primary is unavailable — tests/bdd/features/cluster.feature:682; 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.