Hi @Nataraj ,
Welcome! That GC error suggests that you're hitting a circuit breaker. What is the health and JVM usage of your cluster?
GET _cluster/health
GET _cat/nodes?v=true&h=name,node*,heap*
GET _nodes/stats/breaker
What type of query/ operation are you running when this is triggered? It might be down to the query size.
The below resources may also help you investigate and remediate the problem:
I have ran some queries on ES, which fetched huge amount of data and due to that Memory utilization reached high and ES cluster went down.
Below is the error that ES-java client has thrown
{"error":{"root_cause":[{"type":"circuit_breaking_exception","reason":"[parent] Data too large, data for [<http_request>] would be [4031859746/3.7gb], which is larger than the limit of [3865051136/3.5gb], real usage: [4031859168/3.7gb], new bytes reserved: [578/578b], usages [model_inference=0/0b, inflight_r…
Hope that helps!