# CLUSTER COUNT-FAILURE-REPORTS

> Count the current reports from other nodes that a given node is failing.

URL: https://docs.hotkv.com/commands/cluster-count-failure-reports/

```
CLUSTER COUNT-FAILURE-REPORTS node-id
```

- Group: Cluster
- Complexity: O(N) where N is the number of failure reports
- HotKV Cloud: all plans
- On-Premise: no license needed

`CLUSTER COUNT-FAILURE-REPORTS` returns how many other primaries currently
report the given node as possibly failing, as far as the receiving node has
heard. Reports expire after a multiple of `cluster-node-timeout`, so only
recent ones count. Once enough primaries report a node, it is marked as
failed and one of its replicas can take over, so the count helps you see why
a node is or is not being failed over.

## Return value

| Case | RESP2 | RESP3 |
| --- | --- | --- |
| Known node | Integer: the number of current reports | Integer |
| Unknown node ID | Error `ERR Unknown node <node-id>` | Same error |

## Examples

```
127.0.0.1:6379> CLUSTER COUNT-FAILURE-REPORTS 0e2a97d798979a2e3e5e7f940e2ac533fb36b69b
(integer) 0
127.0.0.1:6379> CLUSTER COUNT-FAILURE-REPORTS 0000000000000000000000000000000000000000
(error) ERR Unknown node 0000000000000000000000000000000000000000
```

## Compatibility

Same as Redis 7 and Valkey 8. It also answers with cluster mode off, where
the only known node is the server itself.

## See also

[CLUSTER NODES](https://docs.hotkv.com/commands/cluster-nodes/index.md), [CLUSTER INFO](https://docs.hotkv.com/commands/cluster-info/index.md),
[CLUSTER FAILOVER](https://docs.hotkv.com/commands/cluster-failover/index.md)

In a cluster: [Monitoring a cluster](https://docs.hotkv.com/clustering/monitoring/index.md)