# Elastic client threads hanging? **URL:** \ **Category:** Elasticsearch\ **Created:** [April 19, 2012, 10:21am UTC](https://discuss.elastic.co/t/elastic-client-threads-hanging/7395 "2012-04-19T10:21:14Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![hillmlogica](https://avatars.discourse-cdn.com/v4/letter/h/a88e4f/32.png) [@hillmlogica](https://discuss.elastic.co/u/hillmlogica)\ **Post date:** [April 19, 2012, 10:21am UTC](https://discuss.elastic.co/t/elastic-client-threads-hanging/7395/1 "2012-04-19T10:21:14Z")
Hi, Our application that runs queries against an Elastic server got itself into an apparent hanging state earlier today. We took a thread dump and can see quite a few elastic threads. We have 4 threads executing Elastic commands, they appear to be in an extended WAITING state, e.g. "Thread t@553". We are not seeing any progress on these WAITING threads - maybe we're missing some sort of timeout? [http://gist.github.com/2420058](http://gist.github.com/2420058) has the dump & the bit of Java code we are executing from the 4 client threads. Thanks in advance for your help. cheers Mike ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [April 19, 2012, 2:57pm UTC](https://discuss.elastic.co/t/elastic-client-threads-hanging/7395/2 "2012-04-19T14:57:12Z")
Sadly, the thread dump on the client side won't help, is there a chance for a recreation? On Thu, Apr 19, 2012 at 1:21 PM, Mike Hill [mikewhill@gmail.com](mailto:mikewhill@gmail.com) wrote: > Hi, > > Our application that runs queries against an Elastic server got itself > into an apparent hanging state earlier today. We took a thread dump > and can see quite a few elastic threads. We have 4 threads executing > Elastic commands, they appear to be in an extended WAITING state, e.g. > "Thread t@553". We are not seeing any progress on these WAITING > threads - maybe we're missing some sort of timeout? > > [Elastic client hang ยท GitHub](http://gist.github.com/2420058) has the dump & the bit of Java code we > are executing from the 4 client threads. > > Thanks in advance for your help. > > cheers > Mike ---
**Author:** ![hillmlogica](https://avatars.discourse-cdn.com/v4/letter/h/a88e4f/32.png) [@hillmlogica](https://discuss.elastic.co/u/hillmlogica)\ **Post date:** [April 19, 2012, 3:16pm UTC](https://discuss.elastic.co/t/elastic-client-threads-hanging/7395/3 "2012-04-19T15:16:12Z")
ok, thanks - i don't think it's easily reproducable, but if it happens again, what other info should we capture to help investigate? -- mike On Apr 19, 3:57 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > Sadly, the thread dump on the client side won't help, is there a chance for > a recreation? > > On Thu, Apr 19, 2012 at 1:21 PM, Mike Hill [mikewh...@gmail.com](mailto:mikewh...@gmail.com) wrote: > > > Hi, > > > Our application that runs queries against an Elastic server got itself > > into an apparent hanging state earlier today. We took a thread dump > > and can see quite a few elastic threads. We have 4 threads executing > > Elastic commands, they appear to be in an extended WAITING state, e.g. > > "Thread t@553". We are not seeing any progress on these WAITING > > threads - maybe we're missing some sort of timeout? > > > [http://gist.github.com/2420058has](http://gist.github.com/2420058has) the dump & the bit of Java code we > > are executing from the 4 client threads. > > > Thanks in advance for your help. > > > cheers > > Mike ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [April 21, 2012, 11:23am UTC](https://discuss.elastic.co/t/elastic-client-threads-hanging/7395/4 "2012-04-21T11:23:09Z")
Because elasticsearch is evented by design, getting an understanding based on things like thread dump and the like does not help much..., so a recreation would be the best bet to get this nailed down as fast as possible. On Thu, Apr 19, 2012 at 6:16 PM, Mike Hill [mikewhill@gmail.com](mailto:mikewhill@gmail.com) wrote: > ok, thanks - i don't think it's easily reproducable, but if it happens > again, what other info should we capture to help investigate? > > -- mike > > On Apr 19, 3:57 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > Sadly, the thread dump on the client side won't help, is there a chance > > for > > a recreation? > > > > On Thu, Apr 19, 2012 at 1:21 PM, Mike Hill [mikewh...@gmail.com](mailto:mikewh...@gmail.com) wrote: > > > > > Hi, > > > > > Our application that runs queries against an Elastic server got itself > > > into an apparent hanging state earlier today. We took a thread dump > > > and can see quite a few elastic threads. We have 4 threads executing > > > Elastic commands, they appear to be in an extended WAITING state, e.g. > > > "Thread t@553". We are not seeing any progress on these WAITING > > > threads - maybe we're missing some sort of timeout? > > > > > [http://gist.github.com/2420058has](http://gist.github.com/2420058has) the dump & the bit of Java code we > > > are executing from the 4 client threads. > > > > > Thanks in advance for your help. > > > > > cheers > > > Mike ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:31am UTC](https://discuss.elastic.co/t/elastic-client-threads-hanging/7395/5 "2017-07-06T03:31:33Z")