mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-06 04:58:50 +00:00
38f5cc236a
In order to be more consistent with what they do, the query cache has been renamed to request cache and the filter cache has been renamed to query cache. A known issue is that package/logger names do no longer match settings names, please speak up if you think this is an issue. Here are the settings for which I kept backward compatibility. Note that they are a bit different from what was discussed on #11569 but putting `cache` before the name of what is cached has the benefit of making these settings consistent with the fielddata cache whose size is configured by `indices.fielddata.cache.size`: * index.cache.query.enable -> index.requests.cache.enable * indices.cache.query.size -> indices.requests.cache.size * indices.cache.filter.size -> indices.queries.cache.size Close #11569
32 lines
981 B
Plaintext
32 lines
981 B
Plaintext
[[indices-clearcache]]
|
|
== Clear Cache
|
|
|
|
The clear cache API allows to clear either all caches or specific cached
|
|
associated with one ore more indices.
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
$ curl -XPOST 'http://localhost:9200/twitter/_cache/clear'
|
|
--------------------------------------------------
|
|
|
|
The API, by default, will clear all caches. Specific caches can be cleaned
|
|
explicitly by setting `query`, `fielddata` or `request`.
|
|
|
|
All caches relating to a specific field(s) can also be cleared by
|
|
specifying `fields` parameter with a comma delimited list of the
|
|
relevant fields.
|
|
|
|
[float]
|
|
=== Multi Index
|
|
|
|
The clear cache 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/_cache/clear'
|
|
|
|
$ curl -XPOST 'http://localhost:9200/_cache/clear'
|
|
--------------------------------------------------
|
|
|