Changed references to riak-admin and riak-repl

Changed references to riak-admin and riak-repl as these are replaced with `riak admin` and `riak repl`.

Author: JMercerGit

content/riak/kv/2.9.1/_reference-links.md

@@ -111,7 +111,7 @@
 [use admin index]: {{<baseurl>}}riak/kv/2.9.1/using/admin/
 [use admin commands]: {{<baseurl>}}riak/kv/2.9.1/using/admin/commands/
 [use admin riak cli]: {{<baseurl>}}riak/kv/2.9.1/using/admin/riak-cli/
-[use admin riak-admin]: {{<baseurl>}}riak/kv/2.9.1/using/admin/riak-admin/
+[use admin riak admin]: {{<baseurl>}}riak/kv/2.9.1/using/admin/riak admin/
 [use admin riak control]: {{<baseurl>}}riak/kv/2.9.1/using/admin/riak-control/
 
 ### Cluster Operations

content/riak/kv/2.9.1/add-ons/redis/developing-rra.md

@@ -72,9 +72,9 @@ an opaque value, ie a `string`. The following command provides an example of
 creating the bucket-type `rra`:
 
 ```sh
-if ! riak-admin bucket-type status rra >/dev/null 2>&1; then
-    riak-admin bucket-type create rra '{"props":{}}'
-    riak-admin bucket-type activate rra
+if ! riak admin bucket-type status rra >/dev/null 2>&1; then
+    riak admin bucket-type create rra '{"props":{}}'
+    riak admin bucket-type activate rra
 fi
 ```
 

content/riak/kv/2.9.1/configuring/basic.md

@@ -17,7 +17,7 @@ aliases:
 
 [config reference]: {{<baseurl>}}riak/kv/2.9.1/configuring/reference
 [use running cluster]: {{<baseurl>}}riak/kv/2.9.1/using/running-a-cluster
-[use admin riak-admin#member-status]: {{<baseurl>}}riak/kv/2.9.1/using/admin/riak-admin/#member-status
+[use admin riak admin#member-status]: {{<baseurl>}}riak/kv/2.9.1/using/admin/riak admin/#member-status
 [perf erlang]: {{<baseurl>}}riak/kv/2.9.1/using/performance/erlang
 [plan start]: {{<baseurl>}}riak/kv/2.9.1/setup/planning/start
 [plan best practices]: {{<baseurl>}}riak/kv/2.9.1/setup/planning/best-practices
@@ -61,7 +61,7 @@ We advise that you make as many of the changes below as practical
 _before_ joining the nodes together into a cluster. Once your
 configuration has been set on each node, follow the steps in [Basic Cluster Setup][use running cluster] to complete the clustering process.
 
-Use [`riak-admin member-status`][use admin riak-admin#member-status]
+Use [`riak admin member-status`][use admin riak admin#member-status]
 to determine whether any given node is a member of a cluster.
 
 ## Erlang VM Tunings
@@ -143,10 +143,10 @@ the location of this file)
 
 ### Verifying ring size
 
-You can use the `riak-admin` command can verify the ring size:
+You can use the `riak admin` command can verify the ring size:
 
 ```bash
-riak-admin status | grep ring
+riak admin status | grep ring
 ```
 
 Console output:

content/riak/kv/2.9.1/configuring/reference.md

@@ -27,7 +27,7 @@ aliases:
 [plan backend multi]: ../../setup/planning/backend/multi
 [config backend multi]: ../../setup/planning/backend/multi/#configuring-multiple-backends-1
 [use admin riak cli]: ../../using/admin/riak-cli
-[use admin riak-admin]: ../../using/admin/riak-admin
+[use admin riak admin]: ../../using/admin/riak admin
 [glossary aae]: ../../learn/glossary/#active-anti-entropy-aae
 [use ref search 2i]: ../../using/reference/secondary-indexes
 [cluster ops bucket types]: ../../using/cluster-operations/bucket-types
@@ -194,7 +194,7 @@ parameters below.
 
 <tr>
 <td><code>platform_bin_dir</code></td>
-<td>The directory in which the <a href="../../using/admin/riak-admin"><code>riak-admin</code></a>,
+<td>The directory in which the <a href="../../using/admin/riak admin"><code>riak admin</code></a>,
 <code>riak-debug</code>, and now-deprecated <code>search-cmd</code>
 executables are stored.</td>
 <td><code>./bin</code></td>

content/riak/kv/2.9.1/configuring/search.md

@@ -133,18 +133,18 @@ Enable this node in distributed query plans; defaults to `on`.
 
 If enabled, this node will participate in distributed Solr queries.  If disabled, the node will be excluded from Riak search cover plans, and will therefore never be consulted in a distributed query.  Note that this node may still be used to execute a query.  Use this flag if you have a long running administrative operation (e.g. reindexing) which requires that the node be removed from query plans, and which would otherwise result in inconsistent search results.
 
-This setting can also be changed via `riak-admin` by issuing one of the following commands:
+This setting can also be changed via `riak admin` by issuing one of the following commands:
 
 ```
-riak-admin set search.dist_query=off
+riak admin set search.dist_query=off
 ```
  or 
 
 ``` 
-riak-admin set search.dist_query=on
+riak admin set search.dist_query=on
 ```
 
-Setting this value in riak.conf is useful when you are restarting a node which was removed from search queries with the `riak-admin` feature. Setting `search.dis_query` in riak.conf will prevent the node from being included in search queries until it is fully spun up.
+Setting this value in riak.conf is useful when you are restarting a node which was removed from search queries with the `riak admin` feature. Setting `search.dis_query` in riak.conf will prevent the node from being included in search queries until it is fully spun up.
 
 Valid values: `on` or `off`
 

content/riak/kv/2.9.1/configuring/strong-consistency.md

@@ -22,8 +22,8 @@ toc: true
 [glossary vnode]: {{<baseurl>}}riak/kv/2.9.1/learn/glossary/#vnode
 [concept buckets]: {{<baseurl>}}riak/kv/2.9.1/learn/concepts/buckets
 [cluster ops bucket types]: {{<baseurl>}}riak/kv/2.9.1/using/cluster-operations/bucket-types
-[use admin riak-admin#ensemble]: {{<baseurl>}}riak/kv/2.9.1/using/admin/riak-admin/#riak-admin-ensemble-status
-[use admin riak-admin]: {{<baseurl>}}riak/kv/2.9.1/using/admin/riak-admin
+[use admin riak admin#ensemble]: {{<baseurl>}}riak/kv/2.9.1/using/admin/riak admin/#riak admin-ensemble-status
+[use admin riak admin]: {{<baseurl>}}riak/kv/2.9.1/using/admin/riak admin
 [config reference#advanced]: {{<baseurl>}}riak/kv/2.9.1/configuring/reference/#advanced-configuration
 [plan cluster capacity]: {{<baseurl>}}riak/kv/2.9.1/setup/planning/cluster-capacity
 [cluster ops strong consistency]: {{<baseurl>}}riak/kv/2.9.1/using/cluster-operations/strong-consistency
@@ -99,7 +99,7 @@ than three nodes, strong consistency will be **enabled** but not yet
 state. Once at least three nodes with strong consistency enabled are
 detected in the cluster, the system will be activated and ready for use.
 You can check on the status of the strong consistency subsystem using
-the [`riak-admin ensemble-status`][use admin riak-admin#ensemble] command.
+the [`riak admin ensemble-status`][use admin riak admin#ensemble] command.
 
 ## Fault Tolerance
 
@@ -136,12 +136,12 @@ of N, i.e. `n_val`, for buckets
 can create and activate a bucket type with N set to 5 and strong
 consistency enabled---we'll call the bucket type
 `consistent_and_fault_tolerant`---using the following series of
-[commands][use admin riak-admin]:
+[commands][use admin riak admin]:
 
 ```bash
-riak-admin bucket-type create consistent_and_fault_tolerant \
+riak admin bucket-type create consistent_and_fault_tolerant \
   '{"props": {"consistent":true,"n_val":5}}'
-riak-admin bucket-type activate consistent_and_fault_tolerant
+riak admin bucket-type activate consistent_and_fault_tolerant
 ```
 
 If the `activate` command outputs `consistent_and_fault_tolerant has
@@ -244,7 +244,7 @@ unable to service strongly consistent operations. The best strategy is
 to reboot nodes one at a time and wait for each node to rejoin existing
 [ensembles][cluster ops strong consistency] before
 continuing to the next node. At any point in time, the state of
-currently existing ensembles can be checked using [`riak-admin ensemble-status`][admin riak-admin#ensemble].
+currently existing ensembles can be checked using [`riak admin ensemble-status`][admin riak admin#ensemble].
 
 ## Performance
 
@@ -263,9 +263,9 @@ can be found in [Adding and Removing Nodes][cluster ops add remove node].
 Your cluster's configuration can also affect strong consistency
 performance. See the section on [configuration][config reference#strong-cons] below.
 
-## riak-admin ensemble-status
+## riak admin ensemble-status
 
-The [`riak-admin`][use admin riak-admin] interface
+The [`riak admin`][use admin riak admin] interface
 used for general node/cluster management has an `ensemble-status`
 command that provides insight into the current status of the consensus
 subsystem undergirding strong consistency.
@@ -274,7 +274,7 @@ Running the command by itself will provide the current state of the
 subsystem:
 
 ```bash
-riak-admin ensemble-status
+riak admin ensemble-status
 ```
 
 If strong consistency is not currently enabled, you will see `Note: The
@@ -332,13 +332,13 @@ ensembles are displayed in the `Ensembles` section of the
 To inspect a specific ensemble, specify the ID:
 
 ```bash
-riak-admin ensemble-status <id>
+riak admin ensemble-status <id>
 ```
 
 The following would inspect ensemble 2:
 
 ```bash
-riak-admin ensemble-status 2
+riak admin ensemble-status 2
 ```
 
 Below is sample output for a single ensemble:

content/riak/kv/2.9.1/configuring/v2-multi-datacenter.md

@@ -102,7 +102,7 @@ Setting | Options | Default | Description
 Setting | Options | Default | Description
 :-------|:--------|:--------|:-----------
 `data_root` | `path` (string) | `data/riak_repl` | Path (relative or absolute) to the working directory for the replication process
-`queue_size` | `bytes` (integer) | `104857600` (100 MiB) | The size of the replication queue in bytes before the replication leader will drop requests. If requests are dropped, a fullsync will be required. Information about dropped requests is available using the `riak-repl status` command
+`queue_size` | `bytes` (integer) | `104857600` (100 MiB) | The size of the replication queue in bytes before the replication leader will drop requests. If requests are dropped, a fullsync will be required. Information about dropped requests is available using the `riak repl status` command
 `server_max_pending` | `max` (integer) | `5` | The maximum number of objects the leader will wait to get an acknowledgment from, from the remote location, before queuing the request
 `vnode_gets` | `true`, `false` | `true` | If `true`, repl will do a direct get against the vnode, rather than use a `GET` finite state machine
 `shuffle_ring` | `true`, `false` | `true `| If `true`, the ring is shuffled randomly. If `false`, the ring is traversed in order. Useful when a sync is restarted to reduce the chance of syncing the same partitions.

content/riak/kv/2.9.1/configuring/v2-multi-datacenter/nat.md

@@ -62,17 +62,17 @@ Server C is set up with a single internal IP address: `192.168.1.20`
 Configure a listener on Server A:
 
 ```bash
-riak-repl add-nat-listener [email protected] 192.168.1.10 9010 50.16.238.123 9011
+riak repl add-nat-listener [email protected] 192.168.1.10 9010 50.16.238.123 9011
 ```
 
 Configure a site (client) on Server B:
 
 ```bash
-riak-repl add-site 50.16.238.123 9011 server_a_to_b
+riak repl add-site 50.16.238.123 9011 server_a_to_b
 ```
 
 Configure a site (client) on Server C:
 
 ```bash
-riak-repl add-site 192.168.1.10 9010 server_a_to_c
+riak repl add-site 192.168.1.10 9010 server_a_to_c
 ```

content/riak/kv/2.9.1/configuring/v2-multi-datacenter/quick-start.md

@@ -66,25 +66,25 @@ addresses would need to be routable over the public Internet.
 ### Set Up the Listeners on Cluster1 (Source cluster)
 
 On a node in Cluster1, `node1` for example, identify the nodes that will
-be listening to connections from replication clients with `riak-repl
+be listening to connections from replication clients with `riak repl
 add-listener <nodename> <listen_ip> <port>` for each node that will be
 listening for replication clients.
 
 ```bash
-riak-repl add-listener [email protected] 172.16.1.11 9010
-riak-repl add-listener [email protected] 172.16.1.12 9010
-riak-repl add-listener [email protected] 172.16.1.13 9010  
+riak repl add-listener [email protected] 172.16.1.11 9010
+riak repl add-listener [email protected] 172.16.1.12 9010
+riak repl add-listener [email protected] 172.16.1.13 9010  
 ```
 
 ### Set Up the Site on Cluster2 (Site cluster)
 
 On a node in Cluster2, `node4` for example, inform the replication
-clients where the Source Listeners are located with `riak-repl add-site
+clients where the Source Listeners are located with `riak repl add-site
 <ipaddr> <port> <sitename>`. Use the IP address(es) and port(s) you
 configured in the earlier step. For `sitename` enter `Cluster1`.
 
 ```bash
-riak-repl add-site 172.16.1.11 9010 Cluster1
+riak repl add-site 172.16.1.11 9010 Cluster1
 ```
 
 **Note**: While a Listener needs to be added to each node, only a single
@@ -94,10 +94,10 @@ Source cluster.
 
 ### Verify the Replication Configuration
 
-Verify the replication configuration using `riak-repl status` on both a
-Cluster1 node and a Cluster2 node. A full description of the `riak-repl
+Verify the replication configuration using `riak repl status` on both a
+Cluster1 node and a Cluster2 node. A full description of the `riak repl
 status` command's output can be found in the documentation for
-`riak-repl`'s [status output][cluster ops v2 mdc#status].
+`riak repl`'s [status output][cluster ops v2 mdc#status].
 
 On the Cluster1 node, verify that there are `listener_<nodename>`s for
 each listening node, and that `leader` and `server_stats` are populated.
@@ -198,33 +198,33 @@ above in the other direction, i.e. from Cluster2 to Cluster1.
 ### Set Up the Listeners on Cluster2 (Source cluster)
 
 On a node in Cluster2, `node4` for example, identify the nodes that will
-be listening to connections from replication clients with `riak-repl
+be listening to connections from replication clients with `riak repl
 add-listener <nodename> <listen_ip> <port>` for each node that will be
 listening for replication clients.
 
 ```bash
-riak-repl add-listener [email protected] 192.168.1.21 9010
-riak-repl add-listener [email protected] 192.168.1.22 9010
-riak-repl add-listener [email protected] 192.168.1.23 9010
+riak repl add-listener [email protected] 192.168.1.21 9010
+riak repl add-listener [email protected] 192.168.1.22 9010
+riak repl add-listener [email protected] 192.168.1.23 9010
 ```
 
 ### Set Up the Site on Cluster1 (Site cluster)
 
 On a node in Cluster1, `node1` for example, inform the replication
-clients where the Source Listeners are with `riak-repl add-site <ipaddr>
+clients where the Source Listeners are with `riak repl add-site <ipaddr>
 <port> <sitename>`. Use the IP address(es) and port(s) you configured in
 the earlier step. For `sitename` enter **Cluster2**.
 
 ```bash
-riak-repl add-site 192.168.1.21 9010 Cluster2
+riak repl add-site 192.168.1.21 9010 Cluster2
 ```
 
 ### Verify the Replication Configuration
 
-Verify the replication configuration using `riak-repl status` on a
-Cluster1 node and a Cluster2 node. A full description of the `riak-repl
+Verify the replication configuration using `riak repl status` on a
+Cluster1 node and a Cluster2 node. A full description of the `riak repl
 status` command's output can be found in the documentation for
-`riak-repl`'s [status output][cluster ops v2 mdc#status].
+`riak repl`'s [status output][cluster ops v2 mdc#status].
 
 On the Cluster1 node, verify that `Cluster2_ips`, `leader`, and
 `client_stats` are populated. They should look similar to the following:
@@ -350,16 +350,16 @@ To start a fullsync operation, issue the following command on your
 leader node:
 
 ```bash
-riak-repl start-fullsync
+riak repl start-fullsync
 ```
 
 A fullsync operation may also be cancelled. If a partition is in
 progress, synchronization will stop after that partition completes.
-During cancellation, `riak-repl status` will show 'cancelled' in the
+During cancellation, `riak repl status` will show 'cancelled' in the
 status.
 
 ```bash
-riak-repl cancel-fullsync
+riak repl cancel-fullsync
 ```
 
 Fullsync operations may also be paused, resumed, or scheduled for

content/riak/kv/2.9.1/configuring/v2-multi-datacenter/ssl.md

@@ -32,10 +32,10 @@ Riak REPL SSL support consists of the following items:
 ## SSL Configuration
 
 To configure SSL, you will need to include the following four settings
-in the `riak-repl` section of your `advanced.config`:
+in the `riak repl` section of your `advanced.config`:
 
 ```advancedconfig
-{riak-repl, [
+{riak repl, [
              % ...
              {ssl_enabled, true},
              {certfile, "/full/path/to/site1-cert.pem"},