How to debug Java Thread Park issues between client process and the AWS Elastic Search?

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 -

  1. What is causing the thread park on the client-side of AWS elastic search?
  2. Which Elastic search thread picked up this request and why it is parked for too long?

Stacktrace on the client side :
sun.misc.Unsafe.park(boolean, long) java.util.concurrent.locks.LockSupport.parkNanos(Object, long) line: 226 java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(int, long) line: 1033 java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(int, long) line: 1326 java.util.concurrent.CountDownLatch.await(long, TimeUnit) line: 282 org.elasticsearch.client.RestClient$SyncResponseListener.get() line: 698 org.elasticsearch.client.RestClient.performRequest(String, String, Map, HttpEntity, HttpAsyncResponseConsumerFactory, Header) line: 224 org.elasticsearch.client.RestClient.InternalperformRequest(String, String, Map, HttpEntity, Header) line: 196

Welcome to our community! :smiley:

Unfortunately we do not support this AWS service, you will probably need to ask their support how to identify performance issues.

Hopefully someone with Springboot experience can chime in around other ideas on the client side.

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.

Adding to the previous answers:

Did you look at Cloud by Elastic, also available if needed from AWS Marketplace ?

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 :slight_smile: ...

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.