Skip to content
HotKVDocs

Ask the HotKV docs

Answers come only from these docs and can be wrong; check the linked pages before you rely on them.

CLUSTER BUMPEPOCH

Last updated 
CLUSTER BUMPEPOCH
Group
Cluster
Complexity
O(N) where N is the number of known nodes
Arity
2 (exactly, counting the command name)
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

Section titled “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

Section titled “Examples”
127.0.0.1:6379> CLUSTER BUMPEPOCH
BUMPED 7
127.0.0.1:6379> CLUSTER BUMPEPOCH
STILL 7

Compatibility

Section titled “Compatibility”

Same behaviour and replies as Redis 7 and Valkey 8.

See also

Section titled “See also”

CLUSTER SET-CONFIG-EPOCH, CLUSTER INFO

In a cluster: Cluster troubleshooting