The FS alert threshold for Elasticsearch volume is not coherent with the default disk-based shard allocation policy
Bug #1595117 reported by
Swann Croiset
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StackLight |
Fix Released
|
Medium
|
Swann Croiset |
Bug Description
Elasticsearch shard allocation depends on available disk space:
low-watermark: 85%
high-watermak: 90%
see https:/
Currently, StackLight thresholds are:
WARN: 10% free space
CRITICAL: 5% free space
The thresholds must be coherent with the ES settings and the operator must be alerted before ES reaches his watermarks:
WARN: 16% free space
CRITICAL: 11% free space
Changed in lma-toolchain: | |
assignee: | nobody → Swann Croiset (swann-w) |
milestone: | none → 0.10.0 |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in lma-toolchain: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is somehow related to https:/ /bugs.launchpad .net/lma- toolchain/ +bug/1587002