From 09436f6c6075bd1795e5e4ab46269f51b827e56e Mon Sep 17 00:00:00 2001
From: Zhichang Yu <yuzhichang@gmail.com>
Date: Tue, 17 Dec 2024 16:48:40 +0800
Subject: [PATCH] Elasticsearch disk-based shard allocator use absolute byte
 values instead of ratio (#4069)

### What problem does this PR solve?

Elasticsearch disk-based shard allocator use absolute byte values
instead of ratio. Close #4018

### Type of change

- [ ] Documentation Update
- [x] Refactoring
---
 docker/docker-compose-base.yml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docker/docker-compose-base.yml b/docker/docker-compose-base.yml
index 5596e4f28..5c5775524 100644
--- a/docker/docker-compose-base.yml
+++ b/docker/docker-compose-base.yml
@@ -17,6 +17,9 @@ services:
       - xpack.security.enabled=true
       - xpack.security.http.ssl.enabled=false
       - xpack.security.transport.ssl.enabled=false
+      - cluster.routing.allocation.disk.watermark.low=5gb
+      - cluster.routing.allocation.disk.watermark.high=3gb
+      - cluster.routing.allocation.disk.watermark.flood_stage=2gb
       - TZ=${TIMEZONE}
     mem_limit: ${MEM_LIMIT}
     ulimits: