Understanding Disk Shard Allocation

corvintheus · April 9, 2019, 10:21pm

Hi, I have a cluster consists of 3 nodes with different sizes of disk. Now, whenever one of the nodes disk reached its high watermark. It seems that it still getting data and continuously going down. I am not sure what is wrong. My current disk size as of the moment is node1 have 100gb, node2 has 300gb and node3 has 1.5TB. Now I am wondering why its not going on node3 even node1 is already complaining about high watermarks? Thanks

cluster.routing.allocation.enable: all
cluster.routing.allocation.disk.threshold_enabled: true
cluster.routing.allocation.disk.watermark.flood_stage: 30gb
cluster.routing.allocation.disk.watermark.low: 100gb
cluster.routing.allocation.disk.watermark.high: 50gb

spinscale · April 11, 2019, 2:28pm

You night want to take a look at the cluster allocation explain API: https://www.elastic.co/guide/en/elasticsearch/reference/7.0/cluster-allocation-explain.html

system · May 9, 2019, 2:28pm

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Understanding Disk-based Shard Allocation better Elasticsearch	11	1196	March 11, 2019
Different disk sizes Elasticsearch	2	856	April 24, 2019
Watermark and shard allocation Elasticsearch	2	698	July 17, 2017
Is there much value in having different values for cluster.routing.allocation.disk.watermark.low/high configs? Elasticsearch	2	501	January 11, 2019
What's the disk watermark actually applied while specified in both node configuration file and cluster settings? Elasticsearch	14	1618	March 23, 2022

Understanding Disk Shard Allocation

Related Topics