You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow opting out of force-merging on a cloned index in ILM's searchable snapshot action (#137375)
In #133954, we modified ILM's searchable snapshot action to perform the
force-merge on a clone of the index with 0 replicas. This optimization
avoids performing the force-merge redundantly on replicas, as the
subsequent snapshot operation only looks at primary shards.
We've seen some cases where cloning the index resulted in issues; there
was a bug in the clone API that caused shards to be initializing
permanently under specific circumstances (fixed by #137096), and cloned
shards are unable to be assigned if their source lives on a node that is
close/past the low watermark disk threshold (will be fixed soon by the
Distributed Coordination team).
Therefore, we implement an opt-out flag that users can configure in the
`searchable_snapshot` action of their ILM policy if they don't want to
clone the index with 0 replicas before performing the force-merge. We
implement an opt-out instead of an opt-in, as we believe these issues to
be rather specific (and soon resolved), and the clone is worth doing by
default.
Copy file name to clipboardExpand all lines: docs/reference/elasticsearch/index-lifecycle-actions/ilm-searchable-snapshot.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,8 +46,11 @@ By default, this snapshot is deleted by the [delete action](/reference/elasticse
46
46
47
47
This force merging occurs in the phase that the index is in **prior** to the `searchable_snapshot` action. For example, if using a `searchable_snapshot` action in the `hot` phase, the force merge will be performed on the hot nodes. If using a `searchable_snapshot` action in the `cold` phase, the force merge will be performed on whatever tier the index is **prior** to the `cold` phase (either `hot` or `warm`).
48
48
49
+
`force_merge_on_clone` {applies_to}`stack: ga 9.2.1`
50
+
: (Optional, Boolean) By default, if `force_merge_index` is `true`, the index will first be cloned with 0 replicas and the force-merge will be performed on the clone before the searchable snapshot is created. This avoids performing the force-merge redundantly on replica shards, as the snapshot operation only uses primary shards. Setting this option to `false` will skip the clone step and perform the force-merge directly on the managed index. Defaults to `true`.
51
+
49
52
`total_shards_per_node`
50
-
: The maximum number of shards (replicas and primaries) that will be allocated to a single node for the searchable snapshot index. Defaults to unbounded.
53
+
: (Optional, Integer) The maximum number of shards (replicas and primaries) that will be allocated to a single node for the searchable snapshot index. Defaults to unbounded.
0 commit comments