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.
Elasticsearch contains multiple circuit breakers used to prevent operations from causing an OutOfMemoryError. Each breaker specifies a limit for how much memory it can use. Additionally, there is a parent-level breaker that specifies the total amount of memory that can be used across all breakers.
These settings can be dynamically updated on a live cluster with the cluster-update-settings API.
The parent-level breaker can be configured with the following setting:
- Starting limit for overall parent breaker, defaults to 70% of JVM heap.
The field data circuit breaker allows Elasticsearch to estimate the amount of memory a field will require to be loaded into memory. It can then prevent the field data loading by raising an exception. By default the limit is configured to 60% of the maximum JVM heap. It can be configured with the following parameters:
- Limit for fielddata breaker, defaults to 60% of JVM heap
- A constant that all field data estimations are multiplied with to determine a final estimation. Defaults to 1.03
The request circuit breaker allows Elasticsearch to prevent per-request data structures (for example, memory used for calculating aggregations during a request) from exceeding a certain amount of memory.
- Limit for request breaker, defaults to 40% of JVM heap
- A constant that all request estimations are multiplied with to determine a final estimation. Defaults to 1
The in flight requests circuit breaker allows Elasticsearch to limit the memory usage of all currently active incoming requests on transport or HTTP level from exceeding a certain amount of memory on a node. The memory usage is based on the content length of the request itself.
- Limit for in flight requests breaker, defaults to 100% of JVM heap. This means that it is bound by the limit configured for the parent circuit breaker.
- A constant that all in flight requests estimations are multiplied with to determine a final estimation. Defaults to 1
The field data cache is used mainly when sorting on or computing aggregations on a field. It loads all the field values to memory in order to provide fast document based access to those values. The field data cache can be expensive to build for a field, so its recommended to have enough memory to allocate it, and to keep it loaded.
The amount of memory used for the field
data cache can be controlled using
reloading the field data which does not fit into your cache will be expensive
and perform poorly.
The max size of the field data cache, eg
30%of node heap space, or an absolute value, eg
12GB. Defaults to unbounded. Also see Field data circuit breaker.
These are static settings which must be configured on every data node in the cluster.
You can monitor memory usage for field data as well as the field data circuit breaker using Nodes Stats API