Elasticsearch disk-based shard allocator use absolute byte values instead of ratio (#4069)
Browse files### 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
CHANGED
|
@@ -17,6 +17,9 @@ services:
|
|
| 17 |
- xpack.security.enabled=true
|
| 18 |
- xpack.security.http.ssl.enabled=false
|
| 19 |
- xpack.security.transport.ssl.enabled=false
|
|
|
|
|
|
|
|
|
|
| 20 |
- TZ=${TIMEZONE}
|
| 21 |
mem_limit: ${MEM_LIMIT}
|
| 22 |
ulimits:
|
|
|
|
| 17 |
- xpack.security.enabled=true
|
| 18 |
- xpack.security.http.ssl.enabled=false
|
| 19 |
- xpack.security.transport.ssl.enabled=false
|
| 20 |
+
- cluster.routing.allocation.disk.watermark.low=5gb
|
| 21 |
+
- cluster.routing.allocation.disk.watermark.high=3gb
|
| 22 |
+
- cluster.routing.allocation.disk.watermark.flood_stage=2gb
|
| 23 |
- TZ=${TIMEZONE}
|
| 24 |
mem_limit: ${MEM_LIMIT}
|
| 25 |
ulimits:
|