Skip to content

Commit 237bc22

Browse files
pjaclarkJMercerGit
pjaclark
and
JMercerGit
authored
Various issues with riak-admin changes and search files fixed (#235) (#236)
* Fixes broken links as a result of riak-admin/riak admin changes Fixes broken links as a result of riak-admin/riak admin changes * leveled_ko/so context leveled_ko/so context, closes #234 * Removes errant search files Pesky search references that got missed previously have been eliminated. This fixes #225 Co-authored-by: James M <[email protected]>
1 parent 0a4ba31 commit 237bc22

File tree

290 files changed

+496
-798
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

290 files changed

+496
-798
lines changed

‎content/riak/kv/3.0.1/configuring/basic.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ aliases:
1818

1919
[config reference]: {{<baseurl>}}riak/kv/3.0.1/configuring/reference
2020
[use running cluster]: {{<baseurl>}}riak/kv/3.0.1/using/running-a-cluster
21-
[use admin riak admin#member-status]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#member-status
21+
[use admin riak admin#member-status]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#member-status
2222
[perf erlang]: {{<baseurl>}}riak/kv/3.0.1/using/performance/erlang
2323
[plan start]: {{<baseurl>}}riak/kv/3.0.1/setup/planning/start
2424
[plan best practices]: {{<baseurl>}}riak/kv/3.0.1/setup/planning/best-practices

‎content/riak/kv/3.0.1/configuring/strong-consistency.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ aliases:
2424
[glossary vnode]: {{<baseurl>}}riak/kv/3.0.1/learn/glossary/#vnode
2525
[concept buckets]: {{<baseurl>}}riak/kv/3.0.1/learn/concepts/buckets
2626
[cluster ops bucket types]: {{<baseurl>}}riak/kv/3.0.1/using/cluster-operations/bucket-types
27-
[use admin riak admin#ensemble]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#ensemble-status
27+
[use admin riak admin#ensemble]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#ensemble-status
2828
[use admin riak admin]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin
2929
[config reference#advanced]: {{<baseurl>}}riak/kv/3.0.1/configuring/reference/#advanced-configuration
3030
[plan cluster capacity]: {{<baseurl>}}riak/kv/3.0.1/setup/planning/cluster-capacity

‎content/riak/kv/3.0.1/learn/dynamo.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1120,7 +1120,7 @@ addressed, however, by the refined partitioning scheme described in Section 6.2.
11201120
> Riak KV operators can trigger node management via the
11211121
> [riak admin command-line tool].
11221122
1123-
[riak admin command-line tool]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/
1123+
[riak admin command-line tool]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/
11241124

11251125
In Amazon’s environment node outages (due to failures and maintenance tasks) are
11261126
often transient but may last for extended intervals. A node outage rarely

‎content/riak/kv/3.0.1/setup/downgrade.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ aliases:
1919
[rolling upgrade]: {{<baseurl>}}riak/kv/3.0.1/setup/upgrading/cluster
2020
[config ref]: {{<baseurl>}}riak/kv/3.0.1/configuring/reference
2121
[concept aae]: {{<baseurl>}}riak/kv/3.0.1/learn/concepts/active-anti-entropy/
22-
[aae status]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#aae-status
22+
[aae status]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#aae-status
2323

2424
Downgrades of Riak KV are tested and supported for two feature release versions, with the general procedure being similar to that of a [rolling upgrade][rolling upgrade].
2525

‎content/riak/kv/3.0.1/setup/planning/cluster-capacity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ aliases:
2020
[plan bitcask capacity]: {{<baseurl>}}riak/kv/3.0.1/setup/planning/bitcask-capacity-calc
2121
[plan index]: {{<baseurl>}}riak/kv/3.0.1/setup/planning
2222
[concept replication]: {{<baseurl>}}riak/kv/3.0.1/learn/concepts/replication
23-
[use admin riak admin#cluster]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster
23+
[use admin riak admin#cluster]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster
2424
[config reference]: {{<baseurl>}}riak/kv/3.0.1/configuring/reference
2525
[perf benchmark]: {{<baseurl>}}riak/kv/3.0.1/using/performance/benchmarking
2626
[LVM]: http://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux)

‎content/riak/kv/3.0.1/using/admin.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ aliases:
1818

1919
[use admin commands]: ./commands/
2020
[use admin riak cli]: ./riak-cli/
21-
[use admin riak admin]: ./riak admin/
21+
[use admin riak admin]: ./riak-admin/
2222
[use admin riak control]: ./riak-control/
2323

2424
## In This Section

‎content/riak/kv/3.0.1/using/admin/commands.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,11 +16,11 @@ aliases:
1616

1717
---
1818

19-
[use admin riak admin#cluster]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster
19+
[use admin riak admin#cluster]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster
2020
[concept clusters]: {{<baseurl>}}riak/kv/3.0.1/learn/concepts/clusters
2121
[cluster ops add remove node]: {{<baseurl>}}riak/kv/3.0.1/using/cluster-operations/adding-removing-nodes
22-
[use admin riak admin#cluster-plan]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster-plan
23-
[use admin riak admin#cluster-commit]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster-commit
22+
[use admin riak admin#cluster-plan]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster-plan
23+
[use admin riak admin#cluster-commit]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster-commit
2424

2525
This document explains usage of the [`riak admin cluster`][use admin riak admin#cluster] interface, which enables you to perform a wide
2626
variety of cluster-level actions.

‎content/riak/kv/3.0.1/using/admin/riak-admin.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ aliases:
3636
[repair recover index]: {{<baseurl>}}riak/kv/3.0.1/using/repair-recovery
3737
[cluster ops strong consistency]: {{<baseurl>}}riak/kv/3.0.1/using/cluster-operations/strong-consistency
3838
[cluster ops handoff]: {{<baseurl>}}riak/kv/3.0.1/using/cluster-operations/handoff
39-
[use admin riak admin#stats]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#stats
39+
[use admin riak admin#stats]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#stats
4040

4141
## `riak admin`
4242

‎content/riak/kv/3.0.1/using/admin/riak-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ aliases:
1818

1919
[configuration file]: {{<baseurl>}}riak/kv/3.0.1/configuring/reference/
2020
[escript]: http://www.erlang.org/doc/man/escript.html
21-
[`riak admin`]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#top
21+
[`riak admin`]: {{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#top
2222
[configuration]: {{<baseurl>}}riak/kv/3.0.1/configuring/reference/
2323

2424
## riak

‎content/riak/kv/3.0.1/using/cluster-operations/backing-up.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ Strong consistency | `/opt/riak/data/ensembles`
126126
## Performing Backups
127127

128128
{{% note title="Deprecation notice" %}}
129-
In previous versions of Riak KV, there was a [`riak admin backup`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#backup) command commonly used for
129+
In previous versions of Riak KV, there was a [`riak admin backup`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#backup) command commonly used for
130130
backups. This functionality is now deprecated. We strongly recommend using the backup procedure documented below instead.
131131
{{% /note %}}
132132

@@ -190,11 +190,11 @@ node that the restored backup was taken from, you will need to
190190
additionally:
191191

192192
1. Mark the original instance down in the cluster using
193-
[`riak admin down <node>`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#down)
193+
[`riak admin down <node>`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#down)
194194
2. Join the restored node to the cluster using
195-
[`riak admin cluster join <node>`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster-join)
195+
[`riak admin cluster join <node>`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster-join)
196196
3. Replace the original instance with the renamed instance with
197-
[`riak admin cluster force-replace <node1> <node2>`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster-force-replace)
197+
[`riak admin cluster force-replace <node1> <node2>`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster-force-replace)
198198
4. Plan the changes to the cluster with `riak admin cluster plan`
199199
5. Finally, commit the cluster changes with `riak admin cluster commit`
200200

‎content/riak/kv/3.0.1/using/cluster-operations/changing-cluster-info.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ To rename a single-node development cluster:
117117

118118
For multi-node clusters, a rename is a slightly more complex procedure; however, it is very similar to the process for renaming a single node.
119119

120-
Previous to Riak version 1.2, a cluster node's name could only be changed with the [`riak admin reip`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#reip) command, which involves downtime for the entire cluster. As of Riak version 1.2, that method has been superseded by [`riak admin cluster force-replace`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster-force-replace), which is safer and does not require cluster wide downtime.
120+
Previous to Riak version 1.2, a cluster node's name could only be changed with the [`riak admin reip`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#reip) command, which involves downtime for the entire cluster. As of Riak version 1.2, that method has been superseded by [`riak admin cluster force-replace`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster-force-replace), which is safer and does not require cluster wide downtime.
121121

122122
There still exist scenarios that require nodes to be renamed while stopped, such as seeding a cluster with backups from another cluster that does not share the same node names. Please see the [Clusters from Backups](#clusters-from-backups) section for more details on renaming in this scenario.
123123

‎content/riak/kv/3.0.1/using/cluster-operations/handoff.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ riak admin handoff disable both --all
6969
## Other Command-line Tools
7070

7171
In addition to enabling and disabling handoff, the
72-
[`riak admin`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/) interface enables you to
72+
[`riak admin`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/) interface enables you to
7373
retrieve a summary of handoff-related activity and other information.
7474

7575
### summary

‎content/riak/kv/3.0.1/using/cluster-operations/inspecting-node.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -473,7 +473,7 @@ you, but here's how to set them:
473473

474474
## Related Resources
475475

476-
* [The riak admin configuration management tool](../../admin/riak admin/)
476+
* [The riak admin configuration management tool](../../admin/riak-admin/)
477477
* [Riaknostic](http://riaknostic.basho.com/)
478478
* [HTTP API Status](../../../developing/api/http/status/)
479479

‎content/riak/kv/3.0.1/using/cluster-operations/replacing-node.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -40,14 +40,14 @@ cluster and have it replace the `riak4` node. We'll call the new node
4040
```
4141

4242
4. Plan the join of the new `riak7` node to an existing node already
43-
participating in the cluster; for example `riak0` with the [`riak admin cluster join`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster) command executed on the new `riak7` node:
43+
participating in the cluster; for example `riak0` with the [`riak admin cluster join`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster) command executed on the new `riak7` node:
4444

4545
```bash
4646
riak admin cluster join riak0
4747
```
4848

4949
5. Plan the replacement of the existing `riak4` node with the new
50-
`riak7` node using the [`riak admin cluster replace`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster) command:
50+
`riak7` node using the [`riak admin cluster replace`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster) command:
5151

5252
```bash
5353
riak admin cluster replace riak4 riak7
@@ -62,30 +62,30 @@ participating in the cluster; for example `riak0` with the [`riak admin cluster
6262
the node has not been joined to a cluster.
6363
</div>
6464

65-
6. Examine the proposed cluster changes with the [`riak admin cluster plan`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster) command executed on the new
65+
6. Examine the proposed cluster changes with the [`riak admin cluster plan`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster) command executed on the new
6666
`riak7` node:
6767

6868
```bash
6969
riak admin cluster plan
7070
```
7171

7272
7. If the changes are correct, you can commit them with the
73-
[`riak admin cluster commit`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster) command:
73+
[`riak admin cluster commit`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster) command:
7474

7575
```bash
7676
riak admin cluster commit
7777
```
7878

79-
If you need to clear the proposed plan and start over, use [`riak admin cluster clear`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster):
79+
If you need to clear the proposed plan and start over, use [`riak admin cluster clear`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster):
8080

8181
```bash
8282
riak admin cluster clear
8383
```
8484

8585
Once you have successfully replaced the node, it should begin leaving
8686
the cluster. You can check on ring readiness after replacing the node
87-
with the [`riak admin ringready`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#ringready)
88-
and [`riak admin member-status`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#member-status)
87+
with the [`riak admin ringready`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#ringready)
88+
and [`riak admin member-status`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#member-status)
8989
commands.
9090

9191
{{% note title="Ring Settling" %}}

‎content/riak/kv/3.0.1/using/cluster-operations/strong-consistency.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ usage in any production environment.
2626
## Monitoring Strong Consistency
2727

2828
Riak provides a wide variety of data related to the current operating
29-
status of a node. This data is available by running the [`riak admin status`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#status) command. That data now
29+
status of a node. This data is available by running the [`riak admin status`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#status) command. That data now
3030
includes statistics specific to strongly consistent operations.
3131

3232
A full listing of these stats is available in [Inspecting a Node]({{<baseurl>}}riak/kv/3.0.1/using/cluster-operations/inspecting-node).

‎content/riak/kv/3.0.1/using/performance/latency-reduction.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ If your use case requires large objects, we recommend checking out
3939
### Mitigation
4040

4141
The best way to find out if large objects are impacting latency is to
42-
monitor each node's object size stats. If you run [`riak admin status`](../../admin/riak admin/#status) or make an HTTP `GET` request
42+
monitor each node's object size stats. If you run [`riak admin status`](../../admin/riak-admin/#status) or make an HTTP `GET` request
4343
to Riak's `/stats` endpoint, you will see the results for the following
4444
metrics related to object size, all of which are calculated only for
4545
`GET` operations (i.e. reads):
@@ -87,7 +87,7 @@ the conflict or until [active anti-entropy](../../../learn/glossary/#active-anti
8787

8888
### Mitigation
8989

90-
The best way to monitor siblings is through the same [`riak admin status`](../../admin/riak admin/#status) interface used to monitor
90+
The best way to monitor siblings is through the same [`riak admin status`](../../admin/riak-admin/#status) interface used to monitor
9191
object size (or via an HTTP `GET` request to `/stats`). In the output of
9292
`riak admin status` in each node, you'll see the following
9393
sibling-related statistics:

‎content/riak/kv/3.0.1/using/reference/custom-code.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ that you do so in a rolling fashion, taking time to ensure that the Riak key
124124
value store has fully initialized and become available for use.
125125

126126
This is done with the `riak admin wait-for-service` command as detailed
127-
in the [Commands documentation]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#wait-for-service).
127+
in the [Commands documentation]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#wait-for-service).
128128

129129
{{% note %}}
130130
It is important that you ensure riak_kv is active before restarting the next

‎content/riak/kv/3.0.1/using/reference/statistics-monitoring.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ aliases:
1818

1919
Riak provides data related to current operating status, which includes
2020
statistics in the form of counters and histograms. These statistics
21-
are made available through the HTTP API via the [`/stats`]({{<baseurl>}}riak/kv/3.0.1/developing/api/http/status) endpoint, or through the [`riak admin`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/) interface, in particular the `stat` and `status` commands.
21+
are made available through the HTTP API via the [`/stats`]({{<baseurl>}}riak/kv/3.0.1/developing/api/http/status) endpoint, or through the [`riak admin`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/) interface, in particular the `stat` and `status` commands.
2222

2323
This page presents the most commonly monitored and gathered
2424
statistics, as well as numerous solutions for monitoring and gathering
@@ -139,7 +139,7 @@ Metric | Also | Notes
139139

140140
## Command-line Interface
141141

142-
The [`riak admin`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/) tool provides two
142+
The [`riak admin`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/) tool provides two
143143
interfaces for retrieving statistics and other information: `status`
144144
and `stat`.
145145

@@ -171,7 +171,7 @@ A comprehensive list of available stats can be found in the
171171
The `riak admin stat` command is related to the `riak admin status`
172172
command but provides a more fine-grained interface for interacting with
173173
stats and information. Full documentation of this command can be found
174-
in the [Inspecting a Node]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#stat) document.
174+
in the [Inspecting a Node]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#stat) document.
175175

176176
## Statistics and Monitoring Tools
177177

‎content/riak/kv/3.0.1/using/running-a-cluster.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ options:
4747
`ring` directory. This will require rejoining all nodes into a
4848
cluster again.
4949
>
50-
> *Rename the node using the [`riak admin cluster replace`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster-replace) command. This will not work if you have previously only started Riak with a single node.
50+
> *Rename the node using the [`riak admin cluster replace`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster-replace) command. This will not work if you have previously only started Riak with a single node.
5151
5252
## Configure the First Node
5353

@@ -154,7 +154,7 @@ preferred.
154154
>
155155
> Once a node has been started, in order to change the name you must
156156
either remove ring files from the `/data/ring` directory or
157-
[`riak admin cluster force-replace`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak admin/#cluster-force-replace) the node.
157+
[`riak admin cluster force-replace`]({{<baseurl>}}riak/kv/3.0.1/using/admin/riak-admin/#cluster-force-replace) the node.
158158

159159
#### Start the node
160160

‎content/riak/kv/3.0.10/_reference-links.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@
101101
[use admin index]: {{<baseurl>}}riak/kv/3.0.10/using/admin/
102102
[use admin commands]: {{<baseurl>}}riak/kv/3.0.10/using/admin/commands/
103103
[use admin riak cli]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak-cli/
104-
[use admin riak admin]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak admin/
104+
[use admin riak admin]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak-admin/
105105
[use admin riak control]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak-control/
106106

107107
### Cluster Operations

‎content/riak/kv/3.0.10/configuring/basic.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ aliases:
1717

1818
[config reference]: {{<baseurl>}}riak/kv/3.0.10/configuring/reference
1919
[use running cluster]: {{<baseurl>}}riak/kv/3.0.10/using/running-a-cluster
20-
[use admin riak admin#member-status]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak admin/#member-status
20+
[use admin riak admin#member-status]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak-admin/#member-status
2121
[perf erlang]: {{<baseurl>}}riak/kv/3.0.10/using/performance/erlang
2222
[plan start]: {{<baseurl>}}riak/kv/3.0.10/setup/planning/start
2323
[plan best practices]: {{<baseurl>}}riak/kv/3.0.10/setup/planning/best-practices

‎content/riak/kv/3.0.10/configuring/strong-consistency.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ toc: true
2222
[glossary vnode]: {{<baseurl>}}riak/kv/3.0.10/learn/glossary/#vnode
2323
[concept buckets]: {{<baseurl>}}riak/kv/3.0.10/learn/concepts/buckets
2424
[cluster ops bucket types]: {{<baseurl>}}riak/kv/3.0.10/using/cluster-operations/bucket-types
25-
[use admin riak admin#ensemble]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak admin/#ensemble-status
25+
[use admin riak admin#ensemble]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak-admin/#ensemble-status
2626
[use admin riak admin]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak admin
2727
[config reference#advanced]: {{<baseurl>}}riak/kv/3.0.10/configuring/reference/#advanced-configuration
2828
[plan cluster capacity]: {{<baseurl>}}riak/kv/3.0.10/setup/planning/cluster-capacity

‎content/riak/kv/3.0.10/learn/dynamo.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1119,7 +1119,7 @@ addressed, however, by the refined partitioning scheme described in Section 6.2.
11191119
> Riak KV operators can trigger node management via the
11201120
> [riak admin command-line tool].
11211121
1122-
[riak admin command-line tool]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak admin/
1122+
[riak admin command-line tool]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak-admin/
11231123

11241124
In Amazon’s environment node outages (due to failures and maintenance tasks) are
11251125
often transient but may last for extended intervals. A node outage rarely

‎content/riak/kv/3.0.10/setup/downgrade.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ aliases:
1818
[rolling upgrade]: {{<baseurl>}}riak/kv/3.0.10/setup/upgrading/cluster
1919
[config ref]: {{<baseurl>}}riak/kv/3.0.10/configuring/reference
2020
[concept aae]: {{<baseurl>}}riak/kv/3.0.10/learn/concepts/active-anti-entropy/
21-
[aae status]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak admin/#aae-status
21+
[aae status]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak-admin/#aae-status
2222

2323
Downgrades of Riak KV are tested and supported for two feature release versions, with the general procedure being similar to that of a [rolling upgrade][rolling upgrade].
2424

‎content/riak/kv/3.0.10/setup/planning/cluster-capacity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ aliases:
1919
[plan bitcask capacity]: {{<baseurl>}}riak/kv/3.0.10/setup/planning/bitcask-capacity-calc
2020
[plan index]: {{<baseurl>}}riak/kv/3.0.10/setup/planning
2121
[concept replication]: {{<baseurl>}}riak/kv/3.0.10/learn/concepts/replication
22-
[use admin riak admin#cluster]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak admin/#cluster
22+
[use admin riak admin#cluster]: {{<baseurl>}}riak/kv/3.0.10/using/admin/riak-admin/#cluster
2323
[config reference]: {{<baseurl>}}riak/kv/3.0.10/configuring/reference
2424
[perf benchmark]: {{<baseurl>}}riak/kv/3.0.10/using/performance/benchmarking
2525
[LVM]: http://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux)

0 commit comments

Comments
 (0)