|
|
@@ -65,9 +65,10 @@ Linux or Storage Spaces on Windows. If you wish to use multiple data paths on a
|
|
|
single machine then you must run one node for each data path.
|
|
|
|
|
|
If you currently use multiple data paths in a
|
|
|
-<<high-availability-cluster-design,highly available cluster>> then you can
|
|
|
-migrate to a setup that uses a single path for each node without downtime using
|
|
|
-a process similar to a <<restart-cluster-rolling,rolling restart>>: shut each
|
|
|
+{ref}/high-availability-cluster-design.html[highly available cluster] then you
|
|
|
+can migrate to a setup that uses a single path for each node without downtime
|
|
|
+using a process similar to a
|
|
|
+{ref}/restart-cluster.html#restart-cluster-rolling[rolling restart]: shut each
|
|
|
node down in turn and replace it with one or more nodes each configured to use
|
|
|
a single data path. In more detail, for each node that currently has multiple
|
|
|
data paths you should follow the following process. In principle you can
|
|
|
@@ -77,7 +78,7 @@ migrating to a single-data-path setup before starting to upgrade.
|
|
|
1. Take a snapshot to protect your data in case of disaster.
|
|
|
|
|
|
2. Optionally, migrate the data away from the target node by using an
|
|
|
-<<cluster-shard-allocation-filtering,allocation filter>>:
|
|
|
+{ref}/modules-cluster.html#cluster-shard-allocation-filtering[allocation filter]:
|
|
|
+
|
|
|
[source,console]
|
|
|
--------------------------------------------------
|
|
|
@@ -89,12 +90,13 @@ PUT _cluster/settings
|
|
|
}
|
|
|
--------------------------------------------------
|
|
|
+
|
|
|
-You can use the <<cat-allocation,cat allocation API>> to track progress of this
|
|
|
-data migration. If some shards do not migrate then the
|
|
|
-<<cluster-allocation-explain,cluster allocation explain API>> will help you to
|
|
|
-determine why.
|
|
|
+You can use the {ref}/cat-allocation.html[cat allocation API] to track progress
|
|
|
+of this data migration. If some shards do not migrate then the
|
|
|
+{ref}/cluster-allocation-explain.html[cluster allocation explain API] will help
|
|
|
+you to determine why.
|
|
|
|
|
|
-3. Follow the steps in the <<restart-cluster-rolling,rolling restart process>>
|
|
|
+3. Follow the steps in the
|
|
|
+{ref}/restart-cluster.html#restart-cluster-rolling[rolling restart process]
|
|
|
up to and including shutting the target node down.
|
|
|
|
|
|
4. Ensure your cluster health is `yellow` or `green`, so that there is a copy
|
|
|
@@ -124,17 +126,18 @@ has sufficient space for the data that it will hold.
|
|
|
`path.data` setting pointing at a separate data path.
|
|
|
|
|
|
9. Start the new nodes and follow the rest of the
|
|
|
-<<restart-cluster-rolling,rolling restart process>> for them.
|
|
|
+{ref}/restart-cluster.html#restart-cluster-rolling[rolling restart process] for
|
|
|
+them.
|
|
|
|
|
|
10. Ensure your cluster health is `green`, so that every shard has been
|
|
|
assigned.
|
|
|
|
|
|
You can alternatively add some number of single-data-path nodes to your
|
|
|
cluster, migrate all your data over to these new nodes using
|
|
|
-<<cluster-shard-allocation-filtering,allocation filters>>, and then remove the
|
|
|
-old nodes from the cluster. This approach will temporarily double the size of
|
|
|
-your cluster so it will only work if you have the capacity to expand your
|
|
|
-cluster like this.
|
|
|
+{ref}/modules-cluster.html#cluster-shard-allocation-filtering[allocation filters],
|
|
|
+and then remove the old nodes from the cluster. This approach will temporarily
|
|
|
+double the size of your cluster so it will only work if you have the capacity to
|
|
|
+expand your cluster like this.
|
|
|
|
|
|
If you currently use multiple data paths but your cluster is not highly
|
|
|
available then the you can migrate to a non-deprecated configuration by taking
|
István Zoltán Szabó