2015-09-17 16:36:25 -04:00
|
|
|
[[indices-forcemerge]]
|
|
|
|
|
== Force Merge
|
|
|
|
|
|
|
|
|
|
The force merge API allows to force merging of one or more indices through an
|
|
|
|
|
API. The merge relates to the number of segments a Lucene index holds within
|
|
|
|
|
each shard. The force merge operation allows to reduce the number of segments by
|
|
|
|
|
merging them.
|
|
|
|
|
|
|
|
|
|
This call will block until the merge is complete. If the http connection is
|
|
|
|
|
lost, the request will continue in the background, and any new requests will
|
|
|
|
|
block until the previous force merge is complete.
|
|
|
|
|
|
|
|
|
|
[source,js]
|
|
|
|
|
--------------------------------------------------
|
2016-09-01 13:05:22 -04:00
|
|
|
POST /twitter/_forcemerge
|
2015-09-17 16:36:25 -04:00
|
|
|
--------------------------------------------------
|
2016-09-01 13:05:22 -04:00
|
|
|
// CONSOLE
|
|
|
|
|
// TEST[setup:twitter]
|
2015-09-17 16:36:25 -04:00
|
|
|
|
|
|
|
|
[float]
|
|
|
|
|
[[forcemerge-parameters]]
|
|
|
|
|
=== Request Parameters
|
|
|
|
|
|
|
|
|
|
The force merge API accepts the following request parameters:
|
|
|
|
|
|
|
|
|
|
[horizontal]
|
|
|
|
|
`max_num_segments`:: The number of segments to merge to. To fully
|
|
|
|
|
merge the index, set it to `1`. Defaults to simply checking if a
|
|
|
|
|
merge needs to execute, and if so, executes it.
|
|
|
|
|
|
|
|
|
|
`only_expunge_deletes`:: Should the merge process only expunge segments with
|
|
|
|
|
deletes in it. In Lucene, a document is not deleted from a segment, just marked
|
|
|
|
|
as deleted. During a merge process of segments, a new segment is created that
|
|
|
|
|
does not have those deletes. This flag allows to only merge segments that have
|
|
|
|
|
deletes. Defaults to `false`. Note that this won't override the
|
|
|
|
|
`index.merge.policy.expunge_deletes_allowed` threshold.
|
|
|
|
|
|
|
|
|
|
`flush`:: Should a flush be performed after the forced merge. Defaults to
|
|
|
|
|
`true`.
|
|
|
|
|
|
2018-05-07 08:54:06 -04:00
|
|
|
[source,js]
|
|
|
|
|
--------------------------------------------------
|
|
|
|
|
POST /kimchy/_forcemerge?only_expunge_deletes=false&max_num_segments=100&flush=true
|
|
|
|
|
--------------------------------------------------
|
2018-05-07 10:09:03 -04:00
|
|
|
// CONSOLE
|
|
|
|
|
// TEST[s/^/PUT kimchy\n/]
|
2018-05-07 08:54:06 -04:00
|
|
|
|
2015-09-17 16:36:25 -04:00
|
|
|
[float]
|
|
|
|
|
[[forcemerge-multi-index]]
|
|
|
|
|
=== Multi Index
|
|
|
|
|
|
|
|
|
|
The force merge API can be applied to more than one index with a single call, or
|
|
|
|
|
even on `_all` the indices.
|
|
|
|
|
|
|
|
|
|
[source,js]
|
|
|
|
|
--------------------------------------------------
|
2016-09-01 13:05:22 -04:00
|
|
|
POST /kimchy,elasticsearch/_forcemerge
|
2015-09-17 16:36:25 -04:00
|
|
|
|
2016-09-01 13:05:22 -04:00
|
|
|
POST /_forcemerge
|
2015-09-17 16:36:25 -04:00
|
|
|
--------------------------------------------------
|
2016-09-01 13:05:22 -04:00
|
|
|
// CONSOLE
|
|
|
|
|
// TEST[s/^/PUT kimchy\nPUT elasticsearch\n/]
|
