WARNING: Version 1.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.

« Clear Cache Refresh »

› ›

Flush

edit

Flush

edit

The flush API allows to flush one or more indices through an API. The flush process of an index basically frees memory from the index by flushing data to the index storage and clearing the internal transaction log. By default, Elasticsearch uses memory heuristics in order to automatically trigger flush operations as required in order to clear memory.

$ curl -XPOST 'http://localhost:9200/twitter/_flush'

Request Parameters

edit

The flush API accepts the following request parameters:

`wait_if_ongoing`	If set to `true` the flush operation will block until the flush can be executed if another flush operation is already executing. The default is `false` and will cause an exception to be thrown on the shard level if another flush operation is already running. [1.4.0.Beta1] Added in 1.4.0.Beta1.
`full`	If set to `true` a new index writer is created and settings that have been changed related to the index writer will be refreshed. Note: if a full flush is required for a setting to take effect this will be part of the settings update process and it not required to be executed by the user. (This setting can be considered as internal)
`force`	Whether a flush should be forced even if it is not necessarily needed ie. if no changes will be committed to the index. This is useful if transaction log IDs should be incremented even if no uncommitted changes are present. (This setting can be considered as internal)

Multi Index

edit

The flush 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/_flush'

$ curl -XPOST 'http://localhost:9200/_flush'

« Clear Cache Refresh »