summaryrefslogtreecommitdiffstats
path: root/iredis/data/commands/replicaof.md
diff options
context:
space:
mode:
Diffstat (limited to 'iredis/data/commands/replicaof.md')
-rw-r--r--iredis/data/commands/replicaof.md28
1 files changed, 14 insertions, 14 deletions
diff --git a/iredis/data/commands/replicaof.md b/iredis/data/commands/replicaof.md
index c8c839c..1c3ec93 100644
--- a/iredis/data/commands/replicaof.md
+++ b/iredis/data/commands/replicaof.md
@@ -1,21 +1,21 @@
-The `REPLICAOF` command can change the replication settings of a replica on the
-fly.
+The `REPLICAOF` command can change the replication settings of a replica on the fly.
-If a Redis server is already acting as replica, the command `REPLICAOF` NO ONE
-will turn off the replication, turning the Redis server into a MASTER. In the
-proper form `REPLICAOF` hostname port will make the server a replica of another
-server listening at the specified hostname and port.
+If a Redis server is already acting as replica, the command `REPLICAOF` NO ONE will turn off the replication, turning the Redis server into a MASTER. In the proper form `REPLICAOF` hostname port will make the server a replica of another server listening at the specified hostname and port.
-If a server is already a replica of some master, `REPLICAOF` hostname port will
-stop the replication against the old server and start the synchronization
-against the new one, discarding the old dataset.
+If a server is already a replica of some master, `REPLICAOF` hostname port will stop the replication against the old server and start the synchronization against the new one, discarding the old dataset.
-The form `REPLICAOF` NO ONE will stop replication, turning the server into a
-MASTER, but will not discard the replication. So, if the old master stops
-working, it is possible to turn the replica into a master and set the
-application to use this new master in read/write. Later when the other Redis
-server is fixed, it can be reconfigured to work as a replica.
+The form `REPLICAOF` NO ONE will stop replication, turning the server into a MASTER, but will not discard the replication. So, if the old master stops working, it is possible to turn the replica into a master and set the application to use this new master in read/write. Later when the other Redis server is fixed, it can be reconfigured to work as a replica.
@return
@simple-string-reply
+
+@examples
+
+```
+> REPLICAOF NO ONE
+"OK"
+
+> REPLICAOF 127.0.0.1 6799
+"OK"
+```