Well,不要刷屏了

ElasticSearch 查询超时错误

Elasticsearch | 作者 Eviltuzki | 发布于2017年07月06日 | 阅读数:13051

1000字左右的morelikethis查询,库中数据量约2100W出头,查询时间很慢,往往在10S以上,昨天看ES日志发现一个错误(昨天刚刚重新索引了数据,通过snapshot进行迁移)。
[2017-07-05 21:48:09,107][WARN ][indices.cluster ] [data85] [[ld.case.0703][0]] marking and sending shard failed due to [failed recovery]
RecoveryFailedException[[ld.case.0703][0]: Recovery failed from {data22}{4MiD-q05QQiPAr1K0Sf0GQ}{10.202.43.22}{10.202.43.22:9300}{master=false} into {data85}{wAr6n38TQmGmrn1OpIOH4Q}{10.202.43.85}{10.202.43.85:9300}{master=false} (no activity after [30m])]; nested: ElasticsearchTimeoutException[no activity after [30m]];
at org.elasticsearch.indices.recovery.RecoveriesCollection$RecoveryMonitor.doRun(RecoveriesCollection.java:235)
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: ElasticsearchTimeoutException[no activity after [30m]]
... 5 more
[2017-07-05 21:48:09,111][WARN ][transport ] [data85] Transport response handler not found of id [3123355]
[2017-07-05 21:48:09,129][WARN ][transport ] [data85] Transport response handler not found of id [3123356]
[2017-07-05 22:48:09,129][WARN ][indices.cluster ] [data85] [[ld.case.0703][0]] marking and sending shard failed due to [failed recovery]
RecoveryFailedException[[ld.case.0703][0]: Recovery failed from {data22}{4MiD-q05QQiPAr1K0Sf0GQ}{10.202.43.22}{10.202.43.22:9300}{master=false} into {data85}{wAr6n38TQmGmrn1OpIOH4Q}{10.202.43.85}{10.202.43.85:9300}{master=false} (no activity after [30m])]; nested: ElasticsearchTimeoutException[no activity after [30m]];
at org.elasticsearch.indices.recovery.RecoveriesCollection$RecoveryMonitor.doRun(RecoveriesCollection.java:235)
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: ElasticsearchTimeoutException[no activity after [30m]]
... 5 more
有人碰到过类似的问题吗?
ES配置挺高的了应该(3个Master 16G,3个DataNode 64G,(heap 30G))
已邀请:

medcl - 今晚打老虎。

赞同来自:

es什么版本?集群恢复没成功啊

puyunjiafly

赞同来自:

官方reindex超时貌似不会一直重试,建议调整集群超时时间,将默认30s的超时时间调整大点
morelikethis我这边测试结果也不怎么理想,有解决方案的话望分享。

chenshoulu

赞同来自:

是你的JVM不够使用了,哥哥
设置jvm.options的
-Xms7g
-Xmx7g
这个大小按照你服务器大小的一半设置

要回复问题请先登录注册