ES error while performing request

最新推荐文章于 2025-01-31 16:25:47 发布

原创最新推荐文章于 2025-01-31 16:25:47 发布 · 1.2w 阅读

1 ·

CC 4.0 BY-SA版权

文章标签：

#error while performing request

ElasticSearch学习专栏收录该内容

1 篇文章

订阅专栏

本文记录了一次在Elasticsearch线上环境中遇到的批量请求异常问题。在测试环境正常运行的情况下，线上环境出现Out of sequence response错误，通过缩短批量执行条数解决了问题。文章详细描述了错误堆栈信息及初步解决方案。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

记录一次Es的报错处理，在测试环境ES的执行没有任何问题，但是到了线上环境，报了如下错误：

ES的通过的RestClient的访问方式的，在网上通过 java.lang.RuntimeException: error while performing request 查询，找到了

https://blog.youkuaiyun.com/wangweislk/article/details/78839384 但是他的错误是因为超时引起的，和我的报错不同，我这边是因为

org.apache.http.HttpException: Out of sequence response

后面同事抓包后，发现报了很多401的错误，怀疑是公司slb的问题，后面直接走ip就没问题了，问题持续观察中..........

当使用http的方式去调用执行，一直会报错，现在把批量执行的条数缩短，就没有再报出相关的问题。

java.lang.RuntimeException: error while performing request
	at org.elasticsearch.client.RestClient$SyncResponseListener.get(RestClient.java:636)
	at org.elasticsearch.client.RestClient.performRequest(RestClient.java:212)
	at org.elasticsearch.client.RestClient.performRequest(RestClient.java:185)
	at com.ctrip.ttd.offlinesearch.service.service.impl.EsServiceImpl.execute(EsServiceImpl.java:56)
	at com.ctrip.ttd.offlinesearch.service.proxy.impl.OptionSearchProxyImpl.createOptionIndex(OptionSearchProxyImpl.java:66)
	at com.ctrip.ttd.offlinesearch.service.service.impl.ImportOptionServiceImpl.dealOptionInfo(ImportOptionServiceImpl.java:197)
	at com.ctrip.ttd.offlinesearch.service.service.impl.ImportOptionServiceImpl.dealOption(ImportOptionServiceImpl.java:109)
	at com.ctrip.ttd.offlinesearch.service.task.SyncOptionEsDataTask.doWork(SyncOptionEsDataTask.java:51)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at qunar.tc.qschedule.config.spring.TaskBean$1.doWork(TaskBean.java:73)
	at qunar.tc.qschedule.executor.SchedulerProvider$2.handleScheduleMessage(SchedulerProvider.java:233)
	at qunar.tc.qschedule.executor.SchedulerProvider$2.onMessage(SchedulerProvider.java:218)
	at qunar.tc.qschedule.executor.ScheduleMessageHandlerImpl$1.run(ScheduleMessageHandlerImpl.java:84)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.http.HttpException: Out of sequence response
	at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.responseReceived(HttpAsyncRequestExecutor.java:267)
	at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:257)
	at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81)
	at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39)
	at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:116)
	at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:164)
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:339)
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:317)
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:278)
	at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
	at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:590)
	... 1 more