2015-11-08 06:59:07 -05:00
|
|
|
[[breaking_20_multiple_literal_data_path_literal_striping]]
|
2015-11-13 16:36:14 -05:00
|
|
|
=== Multiple `path.data` striping
|
2015-08-14 14:26:06 -04:00
|
|
|
|
2015-11-13 16:36:14 -05:00
|
|
|
Previously, if the `path.data` setting listed multiple data paths, then a
|
2015-08-14 14:26:06 -04:00
|
|
|
shard would be ``striped'' across all paths by writing a whole file to each
|
|
|
|
path in turn (in accordance with the `index.store.distributor` setting). The
|
|
|
|
result was that files from a single segment in a shard could be spread across
|
|
|
|
multiple disks, and the failure of any one disk could corrupt multiple shards.
|
|
|
|
|
|
|
|
This striping is no longer supported. Instead, different shards may be
|
|
|
|
allocated to different paths, but all of the files in a single shard will be
|
|
|
|
written to the same path.
|
|
|
|
|
|
|
|
If striping is detected while starting Elasticsearch 2.0.0 or later, *all of
|
|
|
|
the files belonging to the same shard will be migrated to the same path*. If
|
|
|
|
there is not enough disk space to complete this migration, the upgrade will be
|
|
|
|
cancelled and can only be resumed once enough disk space is made available.
|
|
|
|
|
|
|
|
The `index.store.distributor` setting has also been removed.
|
|
|
|
|
|
|
|
|