4185566e93
When using the DiskThresholdDecider, it's possible that shards could already be marked as relocating to the node being evaluated. This commit adds a new setting `cluster.routing.allocation.disk.include_relocations` which adds the size of the shards currently being relocated to this node to the node's used disk space. This new option defaults to `true`, however it's possible to over-estimate the usage for a node if the relocation is already partially complete, for instance: A node with a 10gb shard that's 45% of the way through a relocation would add 10gb + (.45 * 10) = 14.5gb to the node's disk usage before examining the watermarks to see if a new shard can be allocated. Fixes #7753 Relates to #6168 |
||
|---|---|---|
| .. | ||
| community | ||
| groovy-api | ||
| java-api | ||
| javascript | ||
| perl | ||
| python | ||
| reference | ||
| river | ||
| ruby | ||
| README.md | ||
README.md
The Elasticsearch docs are in AsciiDoc format and can be built using the Elasticsearch documentation build process