# Late response on elasticsearch hit **URL:** \ **Category:** Elasticsearch\ **Created:** [February 1, 2017, 9:15pm UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586 "2017-02-01T21:15:24Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Akhilesh\_Anb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akhilesh_anb/32/4343_2.png) [@Akhilesh\_Anb](https://discuss.elastic.co/u/Akhilesh_Anb)\ **Post date:** [February 1, 2017, 9:15pm UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586/1 "2017-02-01T21:15:24Z")
I have an index named "akhil". I'm trying to search as > GET localhost:9200/akhil/\_search It's taking a **20.4sec** time to get the response. I want to know why this is happening. How can I debug this? ---
**Author:** ![Akhilesh\_Anb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akhilesh_anb/32/4343_2.png) [@Akhilesh\_Anb](https://discuss.elastic.co/u/Akhilesh_Anb)\ **Post date:** [February 1, 2017, 10:57pm UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586/2 "2017-02-01T22:57:27Z")
@warkolm please help me ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [February 1, 2017, 11:04pm UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586/3 "2017-02-01T23:04:41Z")
Please provide more details. What search are you running? How much data are you querying? How many shards/indices are you querying? What is the hardware spec of your Elasticsearch cluster? Which version of Elasticsearch are you using? ---
**Author:** ![Akhilesh\_Anb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akhilesh_anb/32/4343_2.png) [@Akhilesh\_Anb](https://discuss.elastic.co/u/Akhilesh_Anb)\ **Post date:** [February 1, 2017, 11:11pm UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586/4 "2017-02-01T23:11:06Z")
We are using ES 2.4.1 It's a 3 node cluster We are querying on one index which contains 200Gb of data. Even when querying on a simple index with 4mb it's taking 2 sec of time to get response. the response times were in the range of few millisecs (1-20)before, now there are responses above 5 seconds, ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [February 2, 2017, 7:40am UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586/5 "2017-02-02T07:40:58Z")
What has changed since you were experiencing low response times? What is the hardware spec of your Elasticsearch cluster? ---
**Author:** ![Akhilesh\_Anb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akhilesh_anb/32/4343_2.png) [@Akhilesh\_Anb](https://discuss.elastic.co/u/Akhilesh_Anb)\ **Post date:** [February 2, 2017, 2:08pm UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586/6 "2017-02-02T14:08:46Z")
Centos, 8 GB ram, 500GB disk ---
**Author:** ![Akhilesh\_Anb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akhilesh_anb/32/4343_2.png) [@Akhilesh\_Anb](https://discuss.elastic.co/u/Akhilesh_Anb)\ **Post date:** [February 2, 2017, 2:24pm UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586/7 "2017-02-02T14:24:28Z")
I executed > GET /\_nodes/hot\_threads Why i'm seeing these errors? Any problem in this? and output is changing everytime ``` ::: {NODE_2}{kweNa7fvRk2SjPyFoGR7PA}{3.3.87.246}{3.3.87.246:9300}{master=true} Hot threads at 2017-02-02T14:37:11.611Z, interval=500ms, busiestThreads=3, ignoreIdleThreads=true: 0.0% (100.5micros out of 500ms) cpu usage by thread 'elasticsearch[NODE_2][transport_client_timer][T#1]{Hashed wheel timer #1}' 10/10 snapshots sharing following 5 elements java.lang.Thread.sleep(Native Method) org.jboss.netty.util.HashedWheelTimer$Worker.waitForNextTick(HashedWheelTimer.java:445) org.jboss.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:364) org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) java.lang.Thread.run(Unknown Source) ::: {NODE_3}{bwtnkXdsR3y6EpKBaNWaRw}{3.3.87.247}{3.3.87.247:9300}{master=true} Hot threads at 2017-02-02T14:37:11.981Z, interval=500ms, busiestThreads=3, ignoreIdleThreads=true: ::: {NODE_1}{MoO58zcVSQOJ1jVrYPtegg}{3.3.87.245}{3.3.87.245:9300}{master=true} Hot threads at 2017-02-02T14:37:11.985Z, interval=500ms, busiestThreads=3, ignoreIdleThreads=true: ``` ---
**Author:** ![Akhilesh\_Anb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akhilesh_anb/32/4343_2.png) [@Akhilesh\_Anb](https://discuss.elastic.co/u/Akhilesh_Anb)\ **Post date:** [February 2, 2017, 2:42pm UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586/8 "2017-02-02T14:42:55Z")
After few minutes im getting this output ``` > ::: {NODE_2}{kweNa7fvRk2SjPyFoGR7PA}{3.3.87.246}{3.3.87.246:9300}{master=true} > Hot threads at 2017-02-02T14:42:16.648Z, interval=500ms, busiestThreads=3, ignoreIdleThreads=true: > ::: {NODE_3}{bwtnkXdsR3y6EpKBaNWaRw}{3.3.87.247}{3.3.87.247:9300}{master=true} > Hot threads at 2017-02-02T14:42:16.972Z, interval=500ms, busiestThreads=3, ignoreIdleThreads=true: > ::: {NODE_1}{MoO58zcVSQOJ1jVrYPtegg}{3.3.87.245}{3.3.87.245:9300}{master=true} > Hot threads at 2017-02-02T14:42:16.977Z, interval=500ms, busiestThreads=3, ignoreIdleThreads=true: ``` ---
**Author:** ![Akhilesh\_Anb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akhilesh_anb/32/4343_2.png) [@Akhilesh\_Anb](https://discuss.elastic.co/u/Akhilesh_Anb)\ **Post date:** [February 2, 2017, 3:03pm UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586/9 "2017-02-02T15:03:25Z")
Updated the latest error > ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [February 2, 2017, 3:09pm UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586/10 "2017-02-02T15:09:14Z")
You said you previously experienced good performance. What has changed since you were experiencing low response times? Is it data volumes? Type of queries? The number of users? ---
**Author:** ![Akhilesh\_Anb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akhilesh_anb/32/4343_2.png) [@Akhilesh\_Anb](https://discuss.elastic.co/u/Akhilesh_Anb)\ **Post date:** [February 2, 2017, 4:01pm UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586/11 "2017-02-02T16:01:13Z")
We are facing latency issue with match\_all query. Users are facing slow response upto ~8 seconds from the application. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 2, 2017, 4:01pm UTC](https://discuss.elastic.co/t/late-response-on-elasticsearch-hit/73586/12 "2017-03-02T16:01:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.