summaryrefslogtreecommitdiffstats
path: root/iredis/data/commands/cluster-bumpepoch.md
diff options
context:
space:
mode:
Diffstat (limited to 'iredis/data/commands/cluster-bumpepoch.md')
-rw-r--r--iredis/data/commands/cluster-bumpepoch.md12
1 files changed, 3 insertions, 9 deletions
diff --git a/iredis/data/commands/cluster-bumpepoch.md b/iredis/data/commands/cluster-bumpepoch.md
index 16a94a4..b05694a 100644
--- a/iredis/data/commands/cluster-bumpepoch.md
+++ b/iredis/data/commands/cluster-bumpepoch.md
@@ -1,15 +1,9 @@
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.
+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.
+**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.
+@simple-string-reply: `BUMPED` if the epoch was incremented, or `STILL` if the node already has the greatest config epoch in the cluster.