CLUSTER-BUMPEPOCH(3valkey)
π CLUSTER-BUMPEPOCH π
okay bestie, welcome to the Valkey Command Manual entry for cluster-bumpepoch β yes it's a real command, yes the name is giving "let's start drama in the cluster" and honestly? it kinda is. sit down, grab a strawberry π, let's get into it.
β¨ NAME β¨
cluster-bumpepoch β advances the cluster config epoch. that's it. that's the whole job. she bumps. she epochs. she slays. π
πΈ SYNOPSIS πΈ
CLUSTER BUMPEPOCH
that's literally it. no args. no flags. a clean, minimal icon. π
π¦ DESCRIPTION π¦
Advances the cluster config epoch. periodt.
So the way this works: the CLUSTER BUMPEPOCH command triggers an increment to the cluster's config epoch from the connected node. and when does that actually happen, you ask? the epoch gets incremented if the node's config epoch is zero, or if it's less than the cluster's greatest epoch. those are the two doors and only one of them needs to be open, iykyk. πͺβ¨
β οΈ okay bestie, real talk for a sec. config epoch management is performed internally by the cluster, and it relies on obtaining a consensus of nodes. CLUSTER BUMPEPOCH attempts to increment the config epoch WITHOUT getting the consensus β which means using it may violate the "last failover wins" rule. so like... use it with caution. this is not a "just try it and see" situation, this is a "know what you're doing" situation. no cap. π
π REPLY π
you get one of these two things back, and both come as a valkey-protocol(7) Bulk string reply:
BUMPEDβ the epoch was incremented. we did it bestie, we bumped. πSTILLβ the node already has the greatest configured epoch in the cluster. so like... nothing to do here, she's already the queen. π
β‘ COMPLEXITY β‘
O(1) β constant time, baby. instant. zero waiting. fast like a group chat notification. π₯
π ACL CATEGORIES π
@admin@dangerous@slow
three categories, and two of them are literally warning labels. that's the energy. π
π HISTORY π
- Available since: 3.0.0
a classic. an elder. she's been here since before it was cool. π«Ά
π§ SEE ALSO π§
go read these too, they're all besties with this one:
asking(3valkey)cluster(3valkey)cluster-addslots(3valkey)cluster-addslotsrange(3valkey)cluster-cancelslotmigrations(3valkey)cluster-count-failure-reports(3valkey)cluster-countkeysinslot(3valkey)cluster-delslots(3valkey)cluster-delslotsrange(3valkey)cluster-failover(3valkey)cluster-flushslots(3valkey)cluster-forget(3valkey)cluster-getkeysinslot(3valkey)cluster-getslotmigrations(3valkey)cluster-help(3valkey)cluster-info(3valkey)cluster-keyslot(3valkey)cluster-links(3valkey)cluster-meet(3valkey)cluster-migrateslots(3valkey)cluster-myid(3valkey)cluster-myshardid(3valkey)cluster-nodes(3valkey)cluster-replicas(3valkey)cluster-replicate(3valkey)cluster-reset(3valkey)cluster-saveconfig(3valkey)cluster-set-config-epoch(3valkey)cluster-setslot(3valkey)cluster-shards(3valkey)cluster-slot-stats(3valkey)cluster-slots(3valkey)cluster-syncslots(3valkey)readonly(3valkey)readwrite(3valkey)
and that's the whole page, bestie!! this one's from version 9.0.0, dated 2025-10-21, and it lives in the CLUSTER-BUMPEPOCH(3valkey) section of the Valkey Command Manual. go forth and bump responsibly. mwah. πβ¨π
π¦ where this page comes from
- fedora 44: valkey-doc 9.0.3-2.fc44 Β· CC-BY-SA-4.0
- fedora 44: valkey-doc 9.0.6-1.fc44 Β· CC-BY-SA-4.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms