Briefly, this error occurs when Elasticsearch is unable to determine the current memory usage due to a known issue in the Java Development Kit (JDK), specifically bug 8207200. This can affect the performance and stability of Elasticsearch. To resolve this issue, you can upgrade your JDK to a version where this bug is fixed. Alternatively, you can adjust the JVM options to limit the memory usage of Elasticsearch, ensuring it doesn’t exceed your system’s capabilities. Lastly, you can monitor your system’s memory usage manually to prevent overconsumption.
This guide will help you check for common problems that cause the log ” Cannot determine current memory usage due to JDK-8207200. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, breaker, memory.
Overview
Elasticsearch has the concept of circuit breakers to deal with OutOfMemory errors that cause nodes to crash. When a request reaches Elasticsearch nodes, the circuit breakers first estimate the amount of memory needed to load the required data. They then compare the estimated size with the configured heap size limit. If the estimated size is greater than the heap size, the query is terminated and an exception is thrown to avoid the node loading more than the available heap size.
What they are used for
Elasticsearch has several circuit breakers available such as fielddata, requests, network, indices and script compilation. Each breaker is used to limit the memory an operation can use. In addition, Elasticsearch has a parent circuit breaker which is used to limit the combined memory used by all the other circuit breakers.
Examples
Increasing circuit breaker size for fielddata limit – The default limit for fielddata breakers is 40%. The following command can be used to increase it to 60%:
PUT /_cluster/settings
{
"persistent": {
"indices.breaker.fielddata.limit": "60%"
}
}Notes
- Each breaker ships with default limits and their limits can be modified as well. But this is an expert level setting and you should understand the pitfalls carefully before changing the limits, otherwise the node may start throwing OOM exceptions.
- Sometimes it is better to fail a query instead of getting an OOM exception, because when OOM appears JVM becomes unresponsive.
- It is important to keep indices.breaker.request.limit lower than indices.breaker.total.limit so that request circuit breakers trip before the total circuit breaker.
Common problems
- The most common error resulting from circuit breakers is “data too large” with 429 status code. The application should be ready to handle such exceptions.
- If the application starts throwing exceptions because of circuit breaker limits, it is important to review the queries and memory requirements. In most cases, a scaling is required by adding more resources to the cluster.
Log Context
Log “Cannot determine current memory usage due to JDK-8207200.” classname is HierarchyCircuitBreakerService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
} catch (IllegalArgumentException ex) {
// This exception can happen (rarely) due to a race condition in the JVM when determining usage of memory pools. We do not want
// to fail requests because of this and thus return zero memory usage in this case. While we could also return the most
// recently determined memory usage; we would overestimate memory usage immediately after a garbage collection event.
assert ex.getMessage().matches("committed = \d+ should be
