Issues regarding status code 429

hey everyone i am facing an problem with the elastic serach service i am facing the problem that i am getting the data -1 ,but whenever i am trying it fetching it for 3 time or more than

does anyone know help inform

It would help if you provided more details about the cluster and the load it is under and exactly when you are seeing these issues.

Please answer the following questions:

  • Which version of Elasticsearch are you using
  • What is the size and specification of your cluster?
  • How much data do you have in your cluster, bith in terms of number of oindices/shards and size in GB on disk?
  • Does the issue occur when indexing and/or querying? Can you provide some more information about the load the cluster is under?

Environment Details

  • Elasticsearch version: (check with GET /)

  • Cluster size/spec: (e.g., 1 node, 2 vCPU, 4 GB RAM, 2 GB heap)

  • Data size: ~45 GB across 12 indices, 36 shards

  • Disk usage: 45 GB on disk

Issue

  • Occurs both when querying (fetching as little as 10 docs) and indexing.

  • Error: circuit_breaking_exception [parent] Data too large → heap usage ~973 MB exceeded breaker limit ~972 MB.

  • Suggests heap memory exhaustion, not query complexity.

Load

  • JVM heap consistently >95%

  • Breaker tripping even for small requests

  • Cluster cannot accept more work until heap is increased or queries optimized

If you are getting 429 responses it is generally a sign that you are overloading the cluster. If you are also seeing circuit breaker issues, you need to increase the heap size. Verify that the heap size is set to 2GB, because the error message makes me suspect it may be just 1GB.

I do not see why you would need 36 shards for 12 indices. A single primary shard per index would likely be more optimal and efficient.

What is the full output of the cluster stats API?

Issue resolved by increasing the heap memory size, thanks @Christian_Dahlqvist