The support for stripping data on more than one path has been available for a very long time now. But since version 2.0.0, it is no longer supported. Instead of data stripping on multiple paths, Elasticsearch now allows you to allocate different shards on different paths. The reason for removing data stripping was that a file from a single segment in a shard could be spread across multiple disks and failure of a single disk could corrupt multiple shards/indices.
The data path is configured inside the
elasticsearch.yml file using the
path.data parameter and similar to version 1.x, you can still use multiple data paths using comma separated values shown as follows:
In this way, all the files belonging to a single shard will be stored at the same path. The other important change based on disk allocation we have already discussed in this chapter, in the Disk-based allocation section, where we mentioned how Elasticsearch now...