Removes the recommendations to use the object field type and to set index: false.
Both of these options are not effective with avoiding mapping explosions.
Today the `current_node` parameter is given in several sample requests
illustrating how to explain an unassigned shard using the cluster
allocation explain API. This doesn't make sense, an unassigned shard has
no `current_node`. This commit removes the misleading parameter in these
cases.
The `high-jvm-memory-pressure.html` troubleshooting docs give some
suggestions, but vitally they omit the advice to capture a heap dump
which is what we really need users to do if they want to understand
their high heap usage. This commit adds a note to the docs to that
effect.
Introduce max headroom settings for the low, high, and flood disk watermark stages, similar to the existing max headroom setting for the flood stage of the frozen tier. Introduce new max headrooms in HealthMetadata and in ReactiveStorageDeciderService. Add multiple tests in DiskThresholdDeciderUnitTests, DiskThresholdDeciderTests and DiskThresholdMonitorTests. Moreover, addition & subtraction for ByteSizeValue, and min.
Felix Barnsteiner
Stef Nestor
David Turner
debadair
Stef Nestor
David Kilfoyle
Abdon Pijpelink
Cleydyr Bezerra de Albuquerque
Ievgen Degtiarenko
Iraklis Psaroudakis
Leaf-Lin