Skip to content

Instantly share code, notes, and snippets.

@ntamvl

ntamvl/low-disk-watermark-exceeded-on.md

Created April 10, 2018 08:43
Show Gist options
  • Save ntamvl/82de20ad99f261c21701c19eb0310aa2 to your computer and use it in GitHub Desktop.
Save ntamvl/82de20ad99f261c21701c19eb0310aa2 to your computer and use it in GitHub Desktop.
Download ZIP
low disk watermark [??%] exceeded on
Raw
low-disk-watermark-exceeded-on.md

low disk watermark [??%] exceeded on

I know it is old post, but my comment can make someone happy. In order to specify watermark in bytes values (gb or mb) you have to add cluster.routing.allocation.disk.watermark.flood_stage to your elasticsearch settings file - elasticsearch.yml. Complete example:

cluster.routing.allocation.disk.threshold_enabled: true 
cluster.routing.allocation.disk.watermark.flood_stage: 200mb
cluster.routing.allocation.disk.watermark.low: 500mb 
cluster.routing.allocation.disk.watermark.high: 300mb

Note: without specifying cluster.routing.allocation.disk.watermark.flood_stage it will not work with bytes value (gb or mb)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment