ILM DOCS: mention forcemerge is best effort (#54794) (#55401)

(cherry picked from commit 3fd05435c52dd265dbe1a40104e7dc7a335d50ae)
Signed-off-by: Andrei Dan <andrei.dan@elastic.co>
This commit is contained in:
Andrei Dan 2020-04-17 15:42:23 +01:00 committed by GitHub
parent 8c581c3388
commit ef338ee3d4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions

View File

@ -301,7 +301,10 @@ Phases allowed: hot, warm.
NOTE: Index will be be made read-only when this action is run NOTE: Index will be be made read-only when this action is run
(see: <<dynamic-index-settings,index.blocks.write>>) (see: <<dynamic-index-settings,index.blocks.write>>)
NOTE: If the `forcemerge` action is used in the `hot` phase, the `rollover` action *must* be preset. NOTE: The `forcemerge` action is best effort. It might happen that some of the
shards are relocating, in which case they will not be merged.
NOTE: If the `forcemerge` action is used in the `hot` phase, the `rollover` action *must* be present.
ILM validates this predicate and will refuse a policy with a forcemerge in the hot phase without a ILM validates this predicate and will refuse a policy with a forcemerge in the hot phase without a
rollover action. rollover action.