# Trace http\_request problem

**URL:** <https://discuss.elastic.co/t/trace-http-request-problem/259410>\
**Category:** Elasticsearch\
**Created:** [December 22, 2020, 4:37pm UTC](https://discuss.elastic.co/t/trace-http-request-problem/259410 "2020-12-22T16:37:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bayucandra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bayucandra/32/81294_2.png) [@bayucandra](https://discuss.elastic.co/u/bayucandra)\
**Post date:** [December 22, 2020, 4:37pm UTC](https://discuss.elastic.co/t/trace-http-request-problem/259410/1 "2020-12-22T16:37:58Z")

</div>

Hi,

I am an elastic cloud user with a budgeted cluster 🙂

Could someone please help me, how to find out which requests to my Elastic search cluster which causing the following problem:

```auto
    {
    "statusCode": 429,
    "error": "Too Many Requests",
    "message": "[circuit_breaking_exception] [parent] Data too large, data for [<http_request>] would be [1035028792/987mb], which is larger than the limit of [1020054732/972.7mb], real usage: [1035028792/987mb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=4441/4.3kb, in_flight_requests=2380822/2.2mb, accounting=65391352/62.3mb], with { bytes_wanted=1035028792 & bytes_limit=1020054732 & durability=\"PERMANENT\" }"
    }

```

I'd like to cut down whichever requests causing that.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 19, 2021, 4:38pm UTC](https://discuss.elastic.co/t/trace-http-request-problem/259410/2 "2021-01-19T16:38:21Z")

</div>

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