honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Document woes between auto-expand-replicas and allocation filtering (#30531) 

Relates to #2869
This commit is contained in:
Yannick Welsch 2018-05-14 12:14:37 +02:00 committed by GitHub
parent 7b95470897
commit c96f2d7bf7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/reference/index-modules.asciidoc
View File

@ -103,9 +103,14 @@ specific index module:
`index.auto_expand_replicas`::
Auto-expand the number of replicas based on the number of available nodes.
Auto-expand the number of replicas based on the number of data nodes in the cluster.
Set to a dash delimited lower and upper bound (e.g. `0-5`) or use `all`
for the upper bound (e.g. `0-all`). Defaults to `false` (i.e. disabled).
for the upper bound (e.g. `0-all`). Defaults to `false` (i.e. disabled).
Note that the auto-expanded number of replicas does not take any other allocation
rules into account, such as <<allocation-awareness,shard allocation awareness>>,
<<shard-allocation-filtering,filtering>> or <<allocation-total-shards,total shards per node>>,
and this can lead to the cluster health becoming `YELLOW` if the applicable rules
prevent all the replicas from being allocated.
`index.search.idle.after`::
How long a shard can not receive a search or get request until it's considered