Advances the cluster config epoch.
CLUSTER
BUMPEPOCH
Advances the cluster config epoch.
The CLUSTER BUMPEPOCH
command triggers an increment to
the cluster’s config epoch from the connected node. The epoch will be
incremented if the node’s config epoch is zero, or if it is less than
the cluster’s greatest epoch.
Note: config epoch management is performed
internally by the cluster, and relies on obtaining a consensus of nodes.
The CLUSTER BUMPEPOCH
attempts to increment the config
epoch WITHOUT getting the consensus, so using it may
violate the “last failover wins” rule. Use it with caution.
One of the following:
Bulk string
reply: BUMPED
if the epoch was incremented.
Bulk string
reply: STILL
if the node already has the greatest
configured epoch in the cluster.
O(1)
@admin @dangerous @slow
ASKING, CLUSTER, CLUSTER ADDSLOTS, CLUSTER ADDSLOTSRANGE, CLUSTER COUNT-FAILURE-REPORTS, CLUSTER COUNTKEYSINSLOT, CLUSTER DELSLOTS, CLUSTER DELSLOTSRANGE, CLUSTER FAILOVER, CLUSTER FLUSHSLOTS, CLUSTER FORGET, CLUSTER GETKEYSINSLOT, CLUSTER HELP, CLUSTER INFO, CLUSTER KEYSLOT, CLUSTER LINKS, CLUSTER MEET, CLUSTER MYID, CLUSTER MYSHARDID, CLUSTER NODES, CLUSTER REPLICAS, CLUSTER REPLICATE, CLUSTER RESET, CLUSTER SAVECONFIG, CLUSTER SET-CONFIG-EPOCH, CLUSTER SETSLOT, CLUSTER SHARDS, CLUSTER SLOT-STATS, CLUSTER SLOTS, READONLY, READWRITE.