WARNING: Version 2.4 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Deprecated in 2.1.0.
Optimize API has been renamed to the force merge API
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.
This call will block until the optimize is complete. If the http connection is lost, the request will continue in the background, and any new requests will block until the previous optimize is complete.
$ curl -XPOST 'http://localhost:9200/twitter/_optimize'
The optimize API accepts the following request parameters as query arguments:
The number of segments to optimize to. To fully
optimize the index, set it to
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
Should a flush be performed after the optimize. Defaults to
The optimize API can be applied to more than one index with a single
call, or even on
_all the indices.
$ curl -XPOST 'http://localhost:9200/kimchy,elasticsearch/_optimize' $ curl -XPOST 'http://localhost:9200/_optimize?only_expunge_deletes=true'
Intro to Kibana
ELK for Logs & Metrics