Recently the Kibana fail to show any content. It just show empty or give us the error. Check the log of Elasticsearch, we found the very long EsRejectedExecutionException
for search queue:
rejected execution of org.elasticsearch.transport.TransportService$7@16130b66 on EsThreadPoolExecutor[search, queue capacity = 1000, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@6c9b1b8d[Running, pool size = 25, active threads = 25, queued tasks = 1832, completed tasks = 200517]]
Following the suggestions from this post, we have checked slow query, gc, io but found nothing.
"gc" : {
"collectors" : {
"young" : {
"collection_count" : 1662,
"collection_time" : "53.1s",
"collection_time_in_millis" : 53169
},
"old" : {
"collection_count" : 1,
"collection_time" : "229ms",
"collection_time_in_millis" : 229
}
}
},
And at the same time, to query node stats it give us:
"search" : {
"threads" : 25,
"queue" : 0,
"active" : 0,
"rejected" : 37364,
"largest" : 25,
"completed" : 204375
It seems that this conflict with the log content: queued task is 0?
By the way, just a simple refresh of Kibana or change of filter will cause very long EsRejectedExecutionException.