ElasticSearch报 EsThreadPoolExecutor[search, queue capacity = 1000, org.elasticsearch.common.util.con...

最新推荐文章于 2022-12-28 16:49:46 发布
转载 最新推荐文章于 2022-12-28 16:49:46 发布 · 607 阅读 · 0 ·
CC 4.0 BY-SA版权
原文链接：http://www.cnblogs.com/haoliansheng/p/5369578.html
文章标签：

#大数据

本文介绍了解决ElasticSearch中因搜索队列容量不足导致的错误的方法。该问题表现为搜索请求被拒绝执行，解决方案是增加搜索队列的容量。

ElasticSearch报以下错误的解决办法：

"type": "es_rejected_execution_exception",
"reason": "rejected execution of org.elasticsearch.transport.TransportService$4@1f9512f on EsThreadPoolExecutor[search, queue capacity = 1000, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@c0efba[Running, pool size = 7, active threads = 7, queued tasks = 1000, completed tasks = 573995]]"

解决方案：

上面报错是因为queue capacity 不行了。需要增加产能：

 

转载于:https://www.cnblogs.com/haoliansheng/p/5369578.html

badiu_30394251
关注
【ElasticSearch】es 线程池 ThreadPool 的封装
九师兄
04-22 1801
10］elasticsearch源码深入分析——线程池的封装。
Elasticsearch 集群升级实战指引—7.x 升级到 8.x
2503_91812631的博客
06-29 1618
升级Elasticsearch集群从7.x到8.x是一项复杂且关键的任务，涉及重大版本变更（如API调整、配置变更、安全功能强制启用等），可能影响集群的性能和稳定性。结合您提到的业务量增长导致索引写入变慢的问题，本指引不仅提供详细的升级步骤，还深入分析写入性能瓶颈的可能原因，并提出针对性优化方案，确保升级后集群性能提升、业务无中断。建议升级到最新补丁版本（如7.17.28，截至2025年6月为7.x系列最新版），因为7.17.x支持直接滚动升级到8.x，且包含关键修复和性能优化。
centos7.6环境下elasticsearch7.5.1客户端创建大量连接队列导致无法响应请求报错 queue capacity = 1000的处理...
reblue520的专栏
05-13 1182
集群环境： centos7.6 + elasticsearch7.5.1 3台集群服务器，三台服务器都是8核32G内存，SSD磁盘，都充当数据节点，一台主节点 现象： es集群状态是绿色，es的磁盘io和cpu使用率都很高，php客户端连接查询超时 集群日志出现大量如下报错： [2020-05-12T21:13:24,612][DEBUG][o.e.a.s.TransportSea...
centos7.6环境下elasticsearch7.5.1无法处理应用的请求报错 queue capacity = 1000的处理
reblue520的专栏
05-13 2653
集群环境： centos7.6 + elasticsearch7.5.1 3台集群服务器，三台服务器都是8核32G内存，SSD磁盘，都充当数据节点，一台主节点 现象： es集群状态是绿色，es的磁盘io和cpu使用率都很高，php客户端连接查询超时 集群日志出现大量如下报错： [2020-05-12T21:13:24,612][DEBUG][o.e.a.s.TransportSea...
开启了1000个线程并发去查询elasticsearch把es搞挂了
weixin_30509393的博客
12-05 1300
org.elasticsearch.transport.RemoteTransportException: [spd-2][172.**.**.**:9300][indices:data/read/search[phase/query]] Caused by: org.elasticsearch.common.util.concurrent.EsRejectedExecutionExcept...
Caused by: org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@fc52803 on QueueResizingEsThreadPoolExecutor[name = a53ad8fb4d74/search, queue capacity = 1000, min queue capacity = 1000, max queue capacity = 1000, frame size = 2000, targeted response rate = 1s, task execution EWMA = 5.7ms, adjustment amount = 50, org.elasticsearch.common.util.concurrent.QueueResizingEsThreadPoolExecutor@2de767db[Running, pool size = 49, active threads = 49, queued tasks = 996, completed tasks = 129731]]", es 单机 如何优化
最新发布
01-06
我们正在处理用户关于在Elasticsearch单机环境下解决EsRejectedExecutionException错误的问题。根据引用[4]，这个错误通常发生在多线程并发写入时，ES达到了并发写入的最大瓶颈。引用[4]中提到，当使用多线程并发...
2025-12-31T00:07:26.637761541Z "stacktrace": ["org.elasticsearch.transport.RemoteTransportException: [a53ad8fb4d74][172.17.0.6:9300][indices:data/read/search[phase/query]]", 2025-12-31T00:07:26.637768696Z "Caused by: org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@fc52803 on QueueResizingEsThreadPoolExecutor[name = a53ad8fb4d74/search, queue capacity = 1000, min queue capacity = 1000, max queue capacity = 1000, frame size = 2000, targeted response rate = 1s, task execution EWMA = 5.7ms, adjustment amount = 50, org.elasticsearch.common.util.concurrent.QueueResizingEsThreadPoolExecutor@2de767db[Running, pool size = 49, active threads = 49, queued tasks = 996, completed tasks = 129731]]", 2025-12-31T00:07:26.637777320Z "at org.elasticsearch.common.util.concurrent.EsAbortPolicy.rejectedExecution(EsAbortPolicy.java:48) ~[elasticsearch-7.6.2.jar:7.6.2]", 2025-12-31T00:07:26.637784254Z "at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:825) ~[?:?]", 2025-12-31T00:07:26.637790753Z "at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1355) ~[?:?]", 2025-12-31T00:07:26.637797794Z "at org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor.execute(EsThreadPoolExecutor.java:84) [elasticsearch-7.6.2.jar:7.6.2]", es 7.6.2 如何解决
01-01
用户问题：如何解决Elasticsearch 7.6.2中出现的`org.elasticsearch.common.util.concurrent.EsRejectedExecutionException`异常？ 分析： 在Elasticsearch中，线程池用于处理各种操作（如搜索、索引、批量操作...
org.elasticsearch.common.util.concurrent.EsThreadPool
07-07
我们正在处理Elasticsearch线程池异常，特别是`org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor`相关的异常。这类异常通常表示线程池资源不足，无法处理更多的任务，可能导致分片分配、索引或搜索...
2025-08-29 20:02:00,016 ERROR [][I/O dispatcher 6][search.client.ElasticSearchClient$1 158] Insert failed org.elasticsearch.ElasticsearchStatusException: Elasticsearch exception [type=es_rejected_execution_exception, reason=rejected execution of org.elasticsearch .action.bulk.TransportBulkAction$1$1@4392fa63 on EsThreadPoolExecutor[name = cmp-192.168.0.163\/write, queue capacity = 10000, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@1ff8f46d[Running, pool size = 16, active threads = 16, queued tasks = 1000 0, completed tasks = 46579255]]] at org.elasticsearch.rest.BytesRestResponse.errorFromXContent(BytesRestResponse.java:187) ~[elasticsearch-1.0.2-c7.10.2-htrunk1.jar:1.0.2-c7.10.2-htrunk1] at org.elasticsearch.client.RestHighLevelClient.parseEntity(RestHighLevelClient.java:1911) ~[elasticsearch-rest-high-level-client-1.0.2-c7.10.2-htrunk1.jar:1.0.2-c7.10.2-htrunk1] at org.elasticsearch.client.RestHighLevelClient.parseResponseException(RestHighLevelClient.java:1888) ~[elasticsearch-rest-high-level-client-1.0.2-c7.10.2-htrunk1.jar:1.0.2-c7.10.2-htrunk1] at org.elasticsearch.client.RestHighLevelClient$1.onFailure(RestHighLevelClient.java:1804) [elasticsearch-rest-high-level-client-1.0.2-c7.10.2-htrunk1.jar:1.0.2-c7.10.2-htrunk1] at org.elasticsearch.client.RestClient$FailureTrackingResponseListener.onDefinitiveFailure(RestClient.java:644) [elasticsearch-rest-client-1.0.2-c7.10.2-htrunk1.jar:1.0.2-c7.10.2-htrunk1] at org.elasticsearch.client.RestClient$1.completed(RestClient.java:386) [elasticsearch-rest-client-1.0.2-c7.10.2-htrunk1.jar:1.0.2-c7.10.2-htrunk1] at org.elasticsearch.client.RestClient$1.completed(RestClient.java:370) [elasticsearch-rest-client-1.0.2-c7.10.2-htrunk1.jar:1.0.2-c7.10.2-htrunk1] at org.apache.http.concurrent.BasicFuture.completed(BasicFuture.java:122) [httpcore-4.4.15.jar:4.4.15] at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:181) [httpasyncclient-4.1.4.jar:4.1.4] at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:448) [httpcore-nio-4.4.15.jar:4.4.15] at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady(HttpAsyncRequestExecutor.java:338) [httpcore-nio-4.4.15.jar:4.4.15] at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:265) [httpcore-nio-4.4.15.jar:4.4.15] at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81) [httpasyncclient-4.1.4.jar:4.1.4] at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39) [httpasyncclient-4.1.4.jar:4.1.4] at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:114) [httpcore-nio-4.4.15.jar:4.4.15] at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162) [httpcore-nio-4.4.15.jar:4.4.15] at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337) [httpcore-nio-4.4.15.jar:4.4.15] at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315) [httpcore-nio-4.4.15.jar:4.4.15] at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276) [httpcore-nio-4.4.15.jar:4.4.15] at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) [httpcore-nio-4.4.15.jar:4.4.15] at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:591) [httpcore-nio-4.4.15.jar:4.4.15] at java.lang.Thread.run(Thread.java:750) [?:1.8.0_452] Suppressed: org.elasticsearch.client.ResponseException: method [POST], host [http://192.168.0.163:7300], URI [/_bulk?timeout=1m], status line [HTTP/1.1 429 Too Many Requests] Warnings: [Parameter [doc_values] has no effect on type [text] and will be removed in future] {"error":{"root_cause":[{"type":"es_rejected_execution_exception","reason":"rejected execution of org.elasticsearch.action.bulk.TransportBulkAction$1$1@4392fa63 on EsThreadPoolExecutor[name = cmp-192.168.0.163/write, queue capacity = 10000, org.elasticsearch.comm on.util.concurrent.EsThreadPoolExecutor@1ff8f46d[Running, pool size = 16, active threads = 16, queued tasks = 10000, completed tasks = 46579255]]"}],"type":"es_rejected_execution_exception","reason":"rejected execution of org.elasticsearch.action.bulk.TransportBu lkAction$1$1@4392fa63 on EsThreadPoolExecutor[name = cmp-192.168.0.163/write, queue capacity = 10000, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@1ff8f46d[Running, pool size = 16, active threads = 16, queued tasks = 10000, completed tasks = 4657 9255]]"},"status":429}
08-30
我们面对的是Elasticsearch在插入数据时出现的"es_rejected_execution_exception"错误。根据引用[2]和[3]，这个错误通常与线程池队列饱和或资源不足有关。具体来说，引用[2]提到“rejected execution of processing ...
java es线程池_探究ElasticSearch中的线程池实现
weixin_36242060的博客
02-27 622
探究ElasticSearch中的线程池实现ElasticSearch里面各种操作都是基于线程池+回调实现的，所以这篇文章记录一下java.util.concurrent涉及线程池实现和ElasticSearch中如何自定义自己的线程池的。因为我们自己开发写代码，也经常会用到线程池，一般很少有机会自己去扩充实现一个自己的线程池，比如下面是我经常用的套路，其中SidSearchExceptionHa...
org.elasticsearch.common.util.concurrent.EsRejectedExecutionException错误解决
u013905744的专栏
09-18 6036
场景： 今天用jmeter来测试搜索服务的并发性能，1000并发，结果es报错了 org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: rejected execution of org.elasticsearch.common.util.concurrent.TimedRunnable@69105af3 ...
线程池ThreadPoolExecutor参数设置
热门推荐
周宏亮G的日志
03-25 9万+
JDK1.5中引入了强大的concurrent包，其中最常用的莫过了线程池的实现ThreadPoolExecutor，它给我们带来了极大的方便，但同时，对于该线程池不恰当的设置也可能使其效率并不能达到预期的效果，甚至仅相当于或低于单线程的效率。 ThreadPoolExecutor类可设置的参数主要有： corePoolSize 核心线程数，核心线程会一直存活，即使没有任务需
es 错误：EsRejectedExecutionException
天空之城
02-15 1万+
错误详情 { "index": { "status": 429, "error": { "type": "es_rejected_execution_exception", "reason": "rejected execution of org.elasticsearch.transport.TransportService$7@637a429f on
Elasticsearch6.4专题之杂记:遇到的异常与解决方案2
天空之蓝的博客
07-27 6790
11、lucene.util.BytesRefHash$MaxBytesLengthExceededException: bytes can be at most 32766 in length; got 56965 解决方案 设置keyword字段的ignore_above为3276512、[ERROR][o.e.a.b.TransportBulkAction] [node-1] failed to execute pipeline for a bulk request org.elasticsearch
ES限流导致ES数据更新不及时问题
半桶水的博客
12-28 1708
es限流
Feign调用异常[Running, pool size = 10, active threads = 10, queued tasks = 0, completed tasks = n]
xzh_blog
07-26 2407
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@1e882e6a rejected from java.util.concurrent.ThreadPoolExecutor@28cdff71[Running, pool size = 10, active threads = 10, queued tasks = 0, completed tasks = 25] at java.uti
java查询es restore_es查询队列挂满，导致es拒绝清切
weixin_39915267的博客
03-02 739
Caused by: org.elasticsearch.common.util.concurrent.EsRejectedExecutionException: rejected execution of org.elasticsearch.transport.TransportService$7@6f3e918 on EsThreadPoolExecutor[search, queue cap...
深入剖析JDK线程池ThreadPool
wwwqg123的博客
01-20 432
前言 线程池是java人员在工作中经遇到的一个技术，也是一个技术难点，最近遇到一个生产环境线程池使用问题，今天特针对源码和平时的工作经验，对ThreadPoolExecutor进行一个全面的剖析 1.问题 1.1 业务场景 业务端直连oss上传的文件结果值，oss会回调到业务服务，然后业务服务处理数据后，将处理后的数据发送到mq供业务端消费以便得到文件上传后的结果值 1.2 问题现象 业务端反馈，...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值