Use case : The Sping boot is calling the AWS Elastic server for the searching for an object through RestHighLevelClient Issue : On the client-side we see Java Thread Parked from 1 to 6 secs
How do I find out -
What is causing the thread park on the client-side of AWS elastic search?
Which Elastic search thread picked up this request and why it is parked for too long?
There's nothing strange on the client side here, this is what I'd expect to see (in versions <7.0) when the client is synchronously waiting for a response from the server. As Mark says, the question of why it's waiting will need to go to the AWS folks, we can't help you with that.
Cloud by elastic is one way to have access to all features, all managed by us. Think about what is there yet like Security, Monitoring, Reporting, SQL, Canvas, Maps UI, Alerting and built-in solutions named Observability, Security, Enterprise Search and what is coming next ...
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.