2013-08-28 19:24:34 -04:00
|
|
|
[[indices-optimize]]
|
|
|
|
|
== Optimize
|
|
|
|
|
|
|
|
|
|
The optimize API allows to optimize one or more indices through an API.
|
|
|
|
|
The optimize process basically optimizes the index for faster search
|
|
|
|
|
operations (and relates to the number of segments a Lucene index holds
|
|
|
|
|
within each shard). The optimize operation allows to reduce the number
|
|
|
|
|
of segments by merging them.
|
|
|
|
|
|
|
|
|
|
[source,js]
|
|
|
|
|
--------------------------------------------------
|
|
|
|
|
$ curl -XPOST 'http://localhost:9200/twitter/_optimize'
|
|
|
|
|
--------------------------------------------------
|
|
|
|
|
|
|
|
|
|
[float]
|
2013-09-30 17:32:00 -04:00
|
|
|
[[optimize-parameters]]
|
2013-08-28 19:24:34 -04:00
|
|
|
=== Request Parameters
|
|
|
|
|
|
|
|
|
|
The optimize API accepts the following request parameters:
|
|
|
|
|
|
2013-09-16 10:12:51 -04:00
|
|
|
[horizontal]
|
|
|
|
|
`max_num_segments`:: The number of segments to optimize to. To fully
|
2013-08-28 19:24:34 -04:00
|
|
|
optimize the index, set it to `1`. Defaults to simply checking if a
|
|
|
|
|
merge needs to execute, and if so, executes it.
|
|
|
|
|
|
2014-06-02 18:49:01 -04:00
|
|
|
`only_expunge_deletes`:: Should the optimize 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.
|
2013-08-28 19:24:34 -04:00
|
|
|
|
2013-09-16 10:12:51 -04:00
|
|
|
`flush`:: Should a flush be performed after the optimize. Defaults to
|
2013-08-28 19:24:34 -04:00
|
|
|
`true`.
|
|
|
|
|
|
2013-09-16 10:12:51 -04:00
|
|
|
`wait_for_merge`:: Should the request wait for the merge to end. Defaults
|
2013-08-28 19:24:34 -04:00
|
|
|
to `true`. Note, a merge can potentially be a very heavy operation, so
|
|
|
|
|
it might make sense to run it set to `false`.
|
|
|
|
|
|
2014-02-28 05:54:45 -05:00
|
|
|
`force`:: Force a merge operation, even if there is a single segment in the
|
2014-03-25 11:57:22 -04:00
|
|
|
shard with no deletions. added[1.1.0]
|
2014-02-28 05:54:45 -05:00
|
|
|
|
2013-08-28 19:24:34 -04:00
|
|
|
[float]
|
2013-09-30 17:32:00 -04:00
|
|
|
[[optimize-multi-index]]
|
2013-08-28 19:24:34 -04:00
|
|
|
=== Multi Index
|
|
|
|
|
|
|
|
|
|
The optimize API can be applied to more than one index with a single
|
|
|
|
|
call, or even on `_all` the indices.
|
|
|
|
|
|
|
|
|
|
[source,js]
|
|
|
|
|
--------------------------------------------------
|
|
|
|
|
$ curl -XPOST 'http://localhost:9200/kimchy,elasticsearch/_optimize'
|
|
|
|
|
|
|
|
|
|
$ curl -XPOST 'http://localhost:9200/_optimize'
|
|
|
|
|
--------------------------------------------------
|
