IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Delete Freeze »
Elastic Docs ›Elasticsearch Guide [7.7] ›ILM: Manage the index lifecycle ›Index lifecycle actions

Force merge

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Force merge

edit

Phases allowed: hot, warm.

Force merges the index into the specified maximum number of segments.

This action makes the index read-only.

To use the forcemerge action in the hot phase, the rollover action must be present. If no rollover action is configured, ILM will reject the policy.

Options

edit
max_num_segments
(Required, integer) Number of segments to merge to. To fully merge the index, set to 1.
codec

(Optional, string) Use the best_compression codec. Valid values: best_compression.

Setting "codec": "best_compression" in the ILM forcemerge action causes {ilm-int} to close and then re-open the index prior to the force merge. During this time, the index is unavailable for both read and write operations.

Example

edit
PUT _ilm/policy/my_policy
{
  "policy": {
    "phases": {
      "warm": {
        "actions": {
          "forcemerge" : {
            "max_num_segments": 1
          }
        }
      }
    }
  }
}
« Delete Freeze »