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

[DOCS] Add info about ILM and unallocated shards. (#56655) (#56724) 

* [DOCS] Add info about ILM and unallocated shards.

* Incorporated review feedback.

* Update docs/reference/ilm/actions/ilm-allocate.asciidoc

Co-authored-by: James Rodewig <james.rodewig@elastic.co>

* Apply suggestions from code review

Co-authored-by: James Rodewig <james.rodewig@elastic.co>

* Fix xref

Co-authored-by: James Rodewig <james.rodewig@elastic.co>

Co-authored-by: James Rodewig <james.rodewig@elastic.co>
This commit is contained in:
debadair 2020-05-13 16:12:37 -07:00 committed by GitHub
parent ab40466bfb
commit 60f8a32dba
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 13 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reference/ilm/actions/ilm-allocate.asciidoc
View File

@ -7,16 +7,16 @@ Phases allowed: warm, cold.
Updates the index settings to change which nodes are allowed to host the index shards
and change the number of replicas.
The allocate action is not allowed in the hot phase.
The initial allocation for the index must be done manually or via
<<indices-templates, index templates>>.
You can configure this action to modify both the allocation rules and number of replicas,
only the allocation rules, or only the number of replicas.
For more information about how {es} uses replicas for scaling, see
<<scalability>>. See <<shard-allocation-filtering>> for more information about
controlling where {es} allocates shards of a particular index.
NOTE: The allocate action is not allowed in the hot phase.
The initial allocation for the index must be done manually or via index templates.
{ilm-init} doesn't handle index allocation during the hot phase.
[[ilm-allocate-options]]
==== Options

9
docs/reference/ilm/ilm-index-lifecycle.asciidoc
View File

@ -36,6 +36,15 @@ the index must be older than the minimum age of the next phase.
The minimum age defaults to zero, which causes {ilm-init} to move indices to the next phase
as soon as all actions in the current phase complete.
If an index has unallocated shards and the <<cluster-health,cluster health status>> is yellow,
the index can still transition to the next phase according to its {ilm} policy.
However, because {es} can only perform certain clean up tasks on a green
cluster, there might be unexpected side effects.
To avoid increased disk usage and reliability issues,
address any cluster health problems in a timely fashion.
[discrete]
[[ilm-phase-execution]]
=== Phase execution