Merge pull request #2243 from basho/ej/kv/vnode-status

Add note on 'riak-admin vnode-status' usage

Author: erjohnson

content/riak/kv/2.0.0/learn/concepts/vnodes.md

@@ -131,11 +131,13 @@ vnodes responsible for the same partition.
 ## Vnode Status
 
 You can check the current status of all vnodes in your cluster using the
-[`riak-admin vnode-status`][use admin riak cli]
-command. When you run that command, you will see a series of reports on
-each of the vnodes active on the local node. The output of this command
-consists of a series of reports on each active vnode. The report for a
-specific vnode should look something like this:
+[`riak-admin vnode-status`][use admin riak cli] command.
+
+{{% note title="Frequent use of `riak-admin vnode-status`" %}}
+The `riak-admin vnode-status` command should not be used more frequently than every 5 minutes. Running it more often will result in handoffs being stalled.
+{{% /note %}}
+
+The output of `riak-admin vnode-status` is a series of reports on each active vnode running on the local node. A report for a specific vnode should look like the following:
 
 ```
 VNode: 1278813932664540053428224228626747642198940975104

content/riak/kv/2.0.0/using/admin/riak-admin.md

@@ -355,6 +355,10 @@ Outputs the status of all vnodes the are running on the local node.
 riak-admin vnode-status
 ```
 
+{{% note title="Frequent use of `riak-admin vnode-status`" %}}
+The `riak-admin vnode-status` command should not be used more frequently than every 5 minutes. Running it more often will result in handoffs being stalled.
+{{% /note %}}
+
 ## aae-status
 
 This command provides insight into operation of Riak's Active

content/riak/kv/2.0.1/learn/concepts/vnodes.md

@@ -131,11 +131,13 @@ vnodes responsible for the same partition.
 ## Vnode Status
 
 You can check the current status of all vnodes in your cluster using the
-[`riak-admin vnode-status`][use admin riak cli]
-command. When you run that command, you will see a series of reports on
-each of the vnodes active on the local node. The output of this command
-consists of a series of reports on each active vnode. The report for a
-specific vnode should look something like this:
+[`riak-admin vnode-status`][use admin riak cli] command.
+
+{{% note title="Frequent use of `riak-admin vnode-status`" %}}
+The `riak-admin vnode-status` command should not be used more frequently than every 5 minutes. Running it more often will result in handoffs being stalled.
+{{% /note %}}
+
+The output of `riak-admin vnode-status` is a series of reports on each active vnode running on the local node. A report for a specific vnode should look like the following:
 
 ```
 VNode: 1278813932664540053428224228626747642198940975104

content/riak/kv/2.0.1/using/admin/riak-admin.md

@@ -355,6 +355,10 @@ Outputs the status of all vnodes the are running on the local node.
 riak-admin vnode-status
 ```
 
+{{% note title="Frequent use of `riak-admin vnode-status`" %}}
+The `riak-admin vnode-status` command should not be used more frequently than every 5 minutes. Running it more often will result in handoffs being stalled.
+{{% /note %}}
+
 ## aae-status
 
 This command provides insight into operation of Riak's Active

content/riak/kv/2.0.2/learn/concepts/vnodes.md

@@ -130,11 +130,13 @@ vnodes responsible for the same partition.
 ## Vnode Status
 
 You can check the current status of all vnodes in your cluster using the
-[`riak-admin vnode-status`][use admin riak cli]
-command. When you run that command, you will see a series of reports on
-each of the vnodes active on the local node. The output of this command
-consists of a series of reports on each active vnode. The report for a
-specific vnode should look something like this:
+[`riak-admin vnode-status`][use admin riak cli] command.
+
+{{% note title="Frequent use of `riak-admin vnode-status`" %}}
+The `riak-admin vnode-status` command should not be used more frequently than every 5 minutes. Running it more often will result in handoffs being stalled.
+{{% /note %}}
+
+The output of `riak-admin vnode-status` is a series of reports on each active vnode running on the local node. A report for a specific vnode should look like the following:
 
 ```
 VNode: 1278813932664540053428224228626747642198940975104

content/riak/kv/2.0.2/using/admin/riak-admin.md

@@ -354,6 +354,10 @@ Outputs the status of all vnodes the are running on the local node.
 riak-admin vnode-status
 ```
 
+{{% note title="Frequent use of `riak-admin vnode-status`" %}}
+The `riak-admin vnode-status` command should not be used more frequently than every 5 minutes. Running it more often will result in handoffs being stalled.
+{{% /note %}}
+
 ## aae-status
 
 This command provides insight into operation of Riak's Active

content/riak/kv/2.0.4/learn/concepts/vnodes.md

@@ -131,11 +131,13 @@ vnodes responsible for the same partition.
 ## Vnode Status
 
 You can check the current status of all vnodes in your cluster using the
-[`riak-admin vnode-status`][use admin riak cli]
-command. When you run that command, you will see a series of reports on
-each of the vnodes active on the local node. The output of this command
-consists of a series of reports on each active vnode. The report for a
-specific vnode should look something like this:
+[`riak-admin vnode-status`][use admin riak cli] command.
+
+{{% note title="Frequent use of `riak-admin vnode-status`" %}}
+The `riak-admin vnode-status` command should not be used more frequently than every 5 minutes. Running it more often will result in handoffs being stalled.
+{{% /note %}}
+
+The output of `riak-admin vnode-status` is a series of reports on each active vnode running on the local node. A report for a specific vnode should look like the following:
 
 ```
 VNode: 1278813932664540053428224228626747642198940975104

content/riak/kv/2.0.4/using/admin/riak-admin.md

@@ -355,6 +355,10 @@ Outputs the status of all vnodes the are running on the local node.
 riak-admin vnode-status
 ```
 
+{{% note title="Frequent use of `riak-admin vnode-status`" %}}
+The `riak-admin vnode-status` command should not be used more frequently than every 5 minutes. Running it more often will result in handoffs being stalled.
+{{% /note %}}
+
 ## aae-status
 
 This command provides insight into operation of Riak's Active

content/riak/kv/2.0.5/learn/concepts/vnodes.md

@@ -131,11 +131,13 @@ vnodes responsible for the same partition.
 ## Vnode Status
 
 You can check the current status of all vnodes in your cluster using the
-[`riak-admin vnode-status`][use admin riak cli]
-command. When you run that command, you will see a series of reports on
-each of the vnodes active on the local node. The output of this command
-consists of a series of reports on each active vnode. The report for a
-specific vnode should look something like this:
+[`riak-admin vnode-status`][use admin riak cli] command.
+
+{{% note title="Frequent use of `riak-admin vnode-status`" %}}
+The `riak-admin vnode-status` command should not be used more frequently than every 5 minutes. Running it more often will result in handoffs being stalled.
+{{% /note %}}
+
+The output of `riak-admin vnode-status` is a series of reports on each active vnode running on the local node. A report for a specific vnode should look like the following:
 
 ```
 VNode: 1278813932664540053428224228626747642198940975104

content/riak/kv/2.0.5/using/admin/riak-admin.md

@@ -355,6 +355,10 @@ Outputs the status of all vnodes the are running on the local node.
 riak-admin vnode-status
 ```
 
+{{% note title="Frequent use of `riak-admin vnode-status`" %}}
+The `riak-admin vnode-status` command should not be used more frequently than every 5 minutes. Running it more often will result in handoffs being stalled.
+{{% /note %}}
+
 ## aae-status
 
 This command provides insight into operation of Riak's Active