summaryrefslogtreecommitdiffstats
path: root/iredis/data/commands/cluster-bumpepoch.md
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2020-03-21 10:28:17 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2021-02-07 11:16:53 +0000
commit06cba6ccd165ca8b224797e37fccb9e63f026d77 (patch)
treee82f1bc439997ae296f2e74f8a64d84c5d95f140 /iredis/data/commands/cluster-bumpepoch.md
parentInitial commit. (diff)
downloadiredis-06cba6ccd165ca8b224797e37fccb9e63f026d77.tar.xz
iredis-06cba6ccd165ca8b224797e37fccb9e63f026d77.zip
Adding upstream version 1.9.1.upstream/1.9.1
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'iredis/data/commands/cluster-bumpepoch.md')
-rw-r--r--iredis/data/commands/cluster-bumpepoch.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/iredis/data/commands/cluster-bumpepoch.md b/iredis/data/commands/cluster-bumpepoch.md
new file mode 100644
index 0000000..16a94a4
--- /dev/null
+++ b/iredis/data/commands/cluster-bumpepoch.md
@@ -0,0 +1,15 @@
+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.
+
+@return
+
+@simple-string-reply: `BUMPED` if the epoch was incremented, or `STILL` if the
+node already has the greatest config epoch in the cluster.