summaryrefslogtreecommitdiffstats
path: root/iredis/data/commands/cluster-slaves.md
diff options
context:
space:
mode:
Diffstat (limited to 'iredis/data/commands/cluster-slaves.md')
-rw-r--r--iredis/data/commands/cluster-slaves.md23
1 files changed, 9 insertions, 14 deletions
diff --git a/iredis/data/commands/cluster-slaves.md b/iredis/data/commands/cluster-slaves.md
index 0b2aa49..d90eaf3 100644
--- a/iredis/data/commands/cluster-slaves.md
+++ b/iredis/data/commands/cluster-slaves.md
@@ -1,21 +1,16 @@
-**A note about the word slave used in this man page and command name**: Starting
-with Redis 5 this command: starting with Redis version 5, if not for backward
-compatibility, the Redis project no longer uses the word slave. Please use the
-new command `CLUSTER REPLICAS`. The command `SLAVEOF` will continue to work for
-backward compatibility.
+**A note about the word slave used in this man page and command name**: starting with Redis version 5, if not for backward compatibility, the Redis project no longer uses the word slave. Please use the new command `CLUSTER REPLICAS`. The command `CLUSTER SLAVES` will continue to work for backward compatibility.
The command provides a list of replica nodes replicating from the specified
-master node. The list is provided in the same format used by `CLUSTER NODES`
-(please refer to its documentation for the specification of the format).
+master node. The list is provided in the same format used by `CLUSTER NODES` (please refer to its documentation for the specification of the format).
-The command will fail if the specified node is not known or if it is not a
-master according to the node table of the node receiving the command.
+The command will fail if the specified node is not known or if it is not
+a master according to the node table of the node receiving the command.
-Note that if a replica is added, moved, or removed from a given master node, and
-we ask `CLUSTER SLAVES` to a node that has not yet received the configuration
-update, it may show stale information. However eventually (in a matter of
-seconds if there are no network partitions) all the nodes will agree about the
-set of nodes associated with a given master.
+Note that if a replica is added, moved, or removed from a given master node,
+and we ask `CLUSTER SLAVES` to a node that has not yet received the
+configuration update, it may show stale information. However eventually
+(in a matter of seconds if there are no network partitions) all the nodes
+will agree about the set of nodes associated with a given master.
@return