# CLUSTER BUMPEPOCH

> Give the receiving node a new configuration epoch, greater than any the cluster knows.

URL: https://docs.hotkv.com/commands/cluster-bumpepoch/

```
CLUSTER BUMPEPOCH
```

- Group: Cluster
- Complexity: O(N) where N is the number of known nodes
- HotKV Cloud: not available
- On-Premise: no license needed

`CLUSTER BUMPEPOCH` gives the receiving node a configuration epoch one
above the greatest epoch it knows of, unless its own epoch is already
non-zero and the greatest. The new epoch is saved to `nodes.conf` and sent
to the other nodes. When two nodes claim the same slot, the one with the
higher epoch wins, so this settles such a conflict in this node's favour.

## Return value

A simple string in RESP2 and RESP3:

| Case | Reply |
| --- | --- |
| The node took a new epoch | `BUMPED <epoch>` |
| Its epoch was already the greatest | `STILL <epoch>` |
| Cluster mode is off | Error `ERR This instance has cluster support disabled` |

## Examples

```
127.0.0.1:6379> CLUSTER BUMPEPOCH
BUMPED 7
127.0.0.1:6379> CLUSTER BUMPEPOCH
STILL 7
```

## Compatibility

Same behaviour and replies as Redis 7 and Valkey 8.

## See also

[CLUSTER SET-CONFIG-EPOCH](https://docs.hotkv.com/commands/cluster-set-config-epoch/index.md),
[CLUSTER INFO](https://docs.hotkv.com/commands/cluster-info/index.md)

In a cluster: [Cluster troubleshooting](https://docs.hotkv.com/clustering/troubleshooting/index.md#nodes-disagree)