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?
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?
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?
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.
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?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.