diff options
| author | Pranith Kumar K <pkarampu@redhat.com> | 2015-04-01 09:06:53 +0530 |
|---|---|---|
| committer | Humble Devassy Chirammal <humble.devassy@gmail.com> | 2015-04-10 03:35:14 +0000 |
| commit | 1c25d5f1492c2186e2c9f468a6c109bd4894fc4f (patch) | |
| tree | c4af45078d5ecab2e2d33f359424ccfd771431c5 | |
| parent | d448fd187dde46bfb0d20354613912f6aa477904 (diff) | |
doc: Fix command parameters in geo-rep doc
Change-Id: Ie408e702999fb40d10f049e5238c64d70cde203e
BUG: 1207939
Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
Reviewed-on: http://review.gluster.org/10081
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
| -rw-r--r-- | doc/admin-guide/en-US/markdown/admin_distributed_geo_rep.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/admin-guide/en-US/markdown/admin_distributed_geo_rep.md b/doc/admin-guide/en-US/markdown/admin_distributed_geo_rep.md index ad44ed55ff8..1be5a8f98b9 100644 --- a/doc/admin-guide/en-US/markdown/admin_distributed_geo_rep.md +++ b/doc/admin-guide/en-US/markdown/admin_distributed_geo_rep.md @@ -77,7 +77,7 @@ This command actually starts the session. Meaning the gsyncd monitor process wil gluster now has variants of status command. ```sh -gluster volume geo-replication <master_volume> <slave_volume>::<slave_volume> status +gluster volume geo-replication <master_volume> <slave_host>::<slave_volume> status ``` This displays the status of session from each brick of the master to each brick of the slave node. @@ -85,7 +85,7 @@ This displays the status of session from each brick of the master to each brick If you want more detailed status, then run 'status detail' ```sh -gluster volume geo-replication <master_volume> <slave_volume>::<slave_volume> status detail +gluster volume geo-replication <master_volume> <slave_host>::<slave_volume> status detail ``` This command displays extra information like, total files synced, files that needs to be synced, deletes pending etc. @@ -95,7 +95,7 @@ This command displays extra information like, total files synced, files that nee This command stops all geo-rep relates processes i.e. gsyncd monitor and works processes. Note that changelog will **not** be turned off with this command. ```sh -gluster volume geo-replication <master_volume> <slave_volume>::<slave_volume> stop [force] +gluster volume geo-replication <master_volume> <slave_host>::<slave_volume> stop [force] ``` Force option is to be used, when one of the node (or glusterd in one of the node) is down. Once stopped, the session can be restarted any time. Note that upon restarting of the session, the change detection mechanism falls back to xsync mode. This happens even though you have changelog generating journals, while the geo-rep session is stopped. @@ -104,7 +104,7 @@ Force option is to be used, when one of the node (or glusterd in one of the node Now you can delete the glusterfs geo-rep session. This will delete all the config data associated with the geo-rep session. ```sh -gluster volume geo-replication <master_volume> <slave_volume>::<slave_volume> delete +gluster volume geo-replication <master_volume> <slave_host>::<slave_volume> delete ``` This deletes all the gsync conf files in each of the nodes. This returns failure, if any of the node is down. And unlike geo-rep stop, there is 'force' option with this. |