Add separate flood stage limit for frozen (#71855)

Dedicated frozen nodes can survive less headroom than other data nodes.
This commits introduces a separate flood stage threshold for frozen as
well as an accompanying max_headroom setting that caps the amount of
free space necessary on frozen.

Relates #71844
This commit is contained in:
Henning Andersen 2021-04-20 15:51:52 +02:00 committed by GitHub
parent 0a2549c12a
commit 794869cfbb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
7 changed files with 268 additions and 12 deletions

View file

@ -113,6 +113,20 @@ PUT /my-index-000001/_settings
--
// end::cluster-routing-flood-stage-tag[]
[[cluster-routing-flood-stage-frozen]]
// tag::cluster-routing-flood-stage-tag[]
`cluster.routing.allocation.disk.watermark.flood_stage.frozen` {ess-icon}::
(<<dynamic-cluster-setting,Dynamic>>)
Controls the flood stage watermark for dedicated frozen nodes, which defaults to
95%.
`cluster.routing.allocation.disk.watermark.flood_stage.frozen.max_headroom` {ess-icon}::
(<<dynamic-cluster-setting,Dynamic>>)
Controls the max headroom for the flood stage watermark for dedicated frozen
nodes. Defaults to 20GB when
`cluster.routing.allocation.disk.watermark.flood_stage.frozen` is not explicitly
set. This caps the amount of free space required on dedicated frozen nodes.
`cluster.info.update.interval`::
(<<dynamic-cluster-setting,Dynamic>>)
How often {es} should check on disk usage for each node in the