Common Elasticsearch Exceptions and How to Resolve Them
1. Request cannot be executed; I/O reactor status: STOPPED
This exception typically occurs when the HTTP client's I/O reactor has been stopped, preventing further requests from being processed. The stack trace shows this happening during Elasticsearch operations.
Caused by: java.lang.RuntimeException: Request cannot be executed; I/O reactor status: STOPPED
at org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:857)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:259)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:246)
at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1613)
at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:1583)
at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:1553)
at org.elasticsearch.client.RestHighLevelClient.search(RestHighLevelClient.java:1069)
at com.deyatech.esutil.service.impl.ElasticSearchServiceImpl.selectDataByESQueryJSON(ElasticSearchServiceImpl.java:581)
at com.deyatech.esutil.service.impl.ElasticSearchServiceImpl.searchData(ElasticSearchServiceImpl.java:548)
at com.deyatech.reception.service.impl.InfoTemplateEsServiceImpl.getElaticsearchResult(InfoTemplateEsServiceImpl.java:251)
at com.deyatech.reception.service.impl.InfoTemplateEsServiceImpl.getTemplateListView(InfoTemplateEsServiceImpl.java:120)
at com.deyatech.reception.service.impl.InfoTemplateServiceImpl.getTemplateListView(InfoTemplateServiceImpl.java:221)
at com.deyatech.reception.service.impl.InfoTemplateServiceImpl$$FastClassBySpringCGLIB$$aadf779.invoke(<generated>)
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:771)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at org.springframework.cache.interceptor.CacheInterceptor.lambda$invoke$0(CacheInterceptor.java:53)
at org.springframework.cache.interceptor.CacheAspectSupport.invokeOperation(CacheAspectSupport.java:366)
at org.springframework.cache.interceptor.CacheAspectSupport.execute(CacheAspectSupport.java:421)
at org.springframework.cache.interceptor.CacheAspectSupport.execute(CacheAspectSupport.java:346)
at org.springframework.cache.interceptor.CacheInterceptor.invoke(CacheInterceptor.java:61)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:691)
at com.deyatech.reception.service.impl.InfoTemplateServiceImpl$$EnhancerBySpringCGLIB$$6d755bd7.getTemplateListView(<generated>)
at com.deyatech.reception.thymeleaf.InfoDataExpressionObject.getInfoList(InfoDataExpressionObject.java:47)
at sun.reflect.GeneratedMethodAccessor1001.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:902)
at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:1547)
... 113 common frames omitted
Caused by: java.lang.IllegalStateException: Request cannot be executed; I/O reactor status: STOPPED
at org.apache.http.util.Asserts.check(Asserts.java:46)
at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.ensureRunning(CloseableHttpAsyncClientBase.java:90)
at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:123)
at org.elasticsearch.client.RestClient.performRequest(RestClient.java:255)
... 143 common frames omitted
Related GitHub issues:
Potetnial solutions:
- Reduce the number of concurrent Elasticsearch clients and ensure proper client management
- Create a new client instance for each thread and close it when finished
- Implement client recreation logic when the connection stops
2. max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
This error occurs when the system's virtual memory configuration is insufficient for Elasticsearch to operate properly.
To resolve this, you need to increase the vm.max_map_count parameter:
# Edit the sysctl configuration file
vi /etc/sysctl.conf
# Add the following line
vm.max_map_count=262144
# Apply the changes
sysctl -p
3. whose UTF8 encoding is longer than the max length 32766
This exception happens when a document contains a term that exceeds the maximum allowed length for UTF-8 encoding.
The error message indicates:
Document contains at least one immense term in field="summary" (whose UTF8 encoding is longer than the max length 32766), all of which were skipped. Please correct the analyzer to not produce such terms.
To fix this, configure the field as a keyword type with an appropriate ignore_above setting:
PUT documents_index/_mapping
{
"properties": {
"description": {
"type": "keyword",
"ignore_above": 10000
}
}
}
Alternatively, using curl:
curl -XPOST http://localhost:9200/documents_index/_mapping -H 'Content-Type:application/json' -d '
{
"properties": {
"description": {
"type": "keyword",
"ignore_above": 10000
}
}
}
'
4. Trying to create too many buckets. Must be less than or equal to: [65536] but was [65537]
This error occurs when a search aggregasion produces more buckets than the configured limit.
To resolve this, increase the search.max_buckets setting:
PUT /_cluster/settings
{
"persistent" : {
"search.max_buckets" : 99999
}
}
To verify the current configuration:
GET _cluster/settings