Browse Source

Remove documentation for multiple data paths (#72267)

relates #71205
Ryan Ernst 4 years ago
parent
commit
99c15cd05a

+ 3 - 3
docs/reference/commands/node-tool.asciidoc

@@ -137,10 +137,10 @@ repaired. If the cluster is still available then you can start up a fresh node
 on another host and {es} will bring this node into the cluster in place of the
 failed node.
 
-Each node stores its data in the data directories defined by the
+Each node stores its data in the data directory defined by the
 <<path-settings,`path.data` setting>>. This means that in a disaster you can
-also restart a node by moving its data directories to another host, presuming
-that those data directories can be recovered from the faulty host.
+also restart a node by moving its data directory to another host, presuming
+that that data directory can be recovered from the faulty host.
 
 {es} <<modules-discovery-quorums,requires a response from a majority of the
 master-eligible nodes>> in order to elect a master and to update the cluster

+ 0 - 16
docs/reference/setup/important-settings/path-settings.asciidoc

@@ -23,19 +23,3 @@ Supported `path.data` and `path.logs` values vary by platform:
 include::{es-repo-dir}/tab-widgets/code.asciidoc[]
 
 include::{es-repo-dir}/tab-widgets/customize-data-log-path-widget.asciidoc[]
-
-[discrete]
-==== Multiple data paths
-deprecated::[7.13.0]
-
-If needed, you can specify multiple paths in `path.data`. {es} stores the node's
-data across all provided paths but keeps each shard's data on the same path.
-
-{es} does not balance shards across a node's data paths. High disk
-usage in a single path can trigger a <<disk-based-shard-allocation,high disk
-usage watermark>> for the entire node. If triggered, {es} will not add shards to
-the node, even if the node’s other paths have available disk space. If you need
-additional disk space, we recommend you add a new node rather than additional
-data paths.
-
-include::{es-repo-dir}/tab-widgets/multi-data-path-widget.asciidoc[]

+ 0 - 39
docs/reference/tab-widgets/multi-data-path-widget.asciidoc

@@ -1,39 +0,0 @@
-++++
-<div class="tabs" data-tab-group="os">
-  <div role="tablist" aria-label="multi-data-path">
-    <button role="tab"
-            aria-selected="true"
-            aria-controls="unix-tab-multi-data-path"
-            id="unix-multi-data-path">
-      Unix-like systems
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="win-tab-multi-data-path"
-            id="win-multi-data-path">
-      Windows
-    </button>
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="unix-tab-multi-data-path"
-       aria-labelledby="unix-multi-data-path">
-++++
-
-include::multi-data-path.asciidoc[tag=unix]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="win-tab-multi-data-path"
-       aria-labelledby="win-multi-data-path"
-       hidden="">
-++++
-
-include::multi-data-path.asciidoc[tag=win]
-
-++++
-  </div>
-</div>
-++++

+ 0 - 26
docs/reference/tab-widgets/multi-data-path.asciidoc

@@ -1,26 +0,0 @@
-// tag::unix[]
-Linux and macOS installations support multiple Unix-style paths in `path.data`:
-
-[source,yaml]
-----
-path:
-  data:
-    - /mnt/elasticsearch_1
-    - /mnt/elasticsearch_2
-    - /mnt/elasticsearch_3
-----
-// end::unix[]
-
-
-// tag::win[]
-Windows installations support multiple DOS paths in `path.data`:
-
-[source,yaml]
-----
-path:
-  data:
-    - "C:\\Elastic\\Elasticsearch_1"
-    - "E:\\Elastic\\Elasticsearch_1"
-    - "F:\\Elastic\\Elasticsearch_3"
-----
-// end::win[]