Elasticsearch: [Docs] Add caveat to `path.data` docs
Describe the feature:
Documentation about [path.data] (https://www.elastic.co/guide/en/elasticsearch/reference/master/path-settings.html) should include a caveat about using this setting for multiple paths unless it's absolutely necessary.
With multiple path.data entries, Elasticsearch does not dynamically load-balance across the different paths, shards are initially allocated based on number of shards per path, shards are never moved between paths once allocated.
In most situations, managing multiple storage paths with a Logical Volume Manager (LVM) might be the recommended option
Elasticsearch version (bin/elasticsearch --version): 7.5
AndyHunt66
All 3 comments
Pinging @elastic/es-docs (>docs)
elasticmachine
on 21 Jan 2020
Pinging @elastic/es-core-infra (:Core/Infra/Packaging)
elasticmachine
on 21 Jan 2020
Another caveat is that high disk usage on one mountpoint marks the whole node under watermark situation. One can end up with a situation when one mountpoint is utilized in 95% and the other is mostly free but still the node cannot take new shards. This behaviour is not intuitive and users looking to expand their storage on a node are surprised that adding more disk space does not help at all.
immon
on 11 Mar 2020
Related issues
jpountz
路
3Comments
matthughes
路
3Comments
makeyang
路
3Comments
dadoonet
路
3Comments
ttaranov
路
3Comments
Most helpful comment
Another caveat is that high disk usage on one mountpoint marks the whole node under watermark situation. One can end up with a situation when one mountpoint is utilized in 95% and the other is mostly free but still the node cannot take new shards. This behaviour is not intuitive and users looking to expand their storage on a node are surprised that adding more disk space does not help at all.