From fc0eeb6e2c25915d63d871d344e3d0b45ea0ea1e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois-Cl=C3=A9ment=20Brossard?= Date: Wed, 16 Oct 2019 20:22:54 +0900 Subject: [PATCH] Clarify low watermark documentation (#48112) Today the docs say that the low watermark has no effect on any shards that have never been allocated, but this is confusing. Here "shard" means "replication group" not "shard copy" but this conflicts with the "never been allocated" qualifier since one allocates shard copies and not replication groups. This commit removes the misleading words. A newly-created replication group remains newly-created until one of its copies is assigned, which might be quite some time later, but it seems better to leave this implicit. --- docs/reference/modules/cluster/disk_allocator.asciidoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/reference/modules/cluster/disk_allocator.asciidoc b/docs/reference/modules/cluster/disk_allocator.asciidoc index 4ff1e5cca215a..be80b6970807f 100644 --- a/docs/reference/modules/cluster/disk_allocator.asciidoc +++ b/docs/reference/modules/cluster/disk_allocator.asciidoc @@ -20,8 +20,7 @@ file or updated dynamically on a live cluster with the 85% disk used. It can also be set to an absolute byte value (like `500mb`) to prevent Elasticsearch from allocating shards if less than the specified amount of space is available. This setting has no effect on the primary - shards of newly-created indices or, specifically, any shards that have - never previously been allocated. + shards of newly-created indices but will prevent their replicas from being allocated. `cluster.routing.allocation.disk.watermark.high`::