Re:Our Favorite Elasticsearch Features, Part 2: Index Aliases
by vasco on Thursday March 01, 2018 @05:25PM
(#16496958)
Meanwhile, my biggest issue with elasticsearch is that for any kind of system where you have indices of different sizes (eg you have several data models being indexed), your cluster will make no attempt at trying to distribute smartly and instead will stop at "same number of indices per node". Which means you very often end up with a very unbalanced cluster with regards to disk usage. For earlier versions there was a plugin that had a smarter allocator, which would look at disk usage when assigning nodes, but for any recent ES cluster (>2.0) you're left with a shrug.
[ Parent
| on HN ]
Re:Our Favorite Elasticsearch Features, Part 2: Index Aliases
by andrewvc on Friday March 02, 2018 @01:17AM
(#16499513)
Have you seen https://www.elastic.co/guide/en/elasticsearch/reference/curr... ? Elasticsearch does take into account disk usage when balancing shards. Perhaps you haven't yet hit the (configurable) high water mark where that rebalancing would occur?
I work for Elastic, but not on Elasticsearch.
Re:Our Favorite Elasticsearch Features, Part 2: Index Aliases
by itruslove on Thursday March 01, 2018 @05:35PM
(#16497037)
Would changing the disk high water mark setting help?
https://www.elastic.co/guide/en/elasticsearch/reference/curr...