# Negative Request Breaker Estimated Size **URL:** \ **Category:** Elasticsearch\ **Created:** [November 3, 2025, 12:23pm UTC](https://discuss.elastic.co/t/negative-request-breaker-estimated-size/383184 "2025-11-03T12:23:04Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Aditya\_Teltia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aditya_teltia/32/122447_2.png) [@Aditya\_Teltia](https://discuss.elastic.co/u/Aditya_Teltia)\ **Post date:** [November 3, 2025, 12:23pm UTC](https://discuss.elastic.co/t/negative-request-breaker-estimated-size/383184/1 "2025-11-03T12:23:04Z")
Hi Everyone, I am using ES-8.15.5 and while using this in production I am getting negative value of requests circuit breaker estimated\_size\_in\_bytes. Not able to reproduce this locally either. I am having hard time identifying the cause for this. Can someone please help on how can I identify the cause for this? ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/8/3808f72a4df3ec795427dba00dda39f24e311105.png) I turned on Trace logging for a while and got logs similar to this of addition or subtraction: `[request] Adjusted breaker by [-16472] bytes, now [-9914192]` Let me know if any other detail is required here. ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [November 3, 2025, 5:04pm UTC](https://discuss.elastic.co/t/negative-request-breaker-estimated-size/383184/2 "2025-11-03T17:04:50Z")
This is a definite bug; you’re using a version that’s almost a year old now, can you upgrade and see if it’s been fixed in the meantime? ---
**Author:** ![Aditya\_Teltia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aditya_teltia/32/122447_2.png) [@Aditya\_Teltia](https://discuss.elastic.co/u/Aditya_Teltia)\ **Post date:** [November 4, 2025, 7:15am UTC](https://discuss.elastic.co/t/negative-request-breaker-estimated-size/383184/3 "2025-11-04T07:15:53Z")
Actually we recently moved from 7.17.6 to 8.15.5, so really can’t move immediately. Is it possible to find this Issue or Its PR on github? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [November 4, 2025, 8:18am UTC](https://discuss.elastic.co/t/negative-request-breaker-estimated-size/383184/4 "2025-11-04T08:18:49Z")
IMO it was a mistake to upgrade to a version that was so old, and it’s worth upgrading again ASAP. I’m not going to go through the last year’s worth of changes looking for a possible explanation. ---
**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\ **Post date:** [November 4, 2025, 10:30am UTC](https://discuss.elastic.co/t/negative-request-breaker-estimated-size/383184/5 "2025-11-04T10:30:41Z")
Aside from the log entry, are you seeing any issues with your cluster ? Is `tripped` always zero ? > [@Aditya\_Teltia](#): > > Actually we recently moved from 7.17.6 to 8.15.5, so really can’t move immediately. Is it possible to find this Issue or Its PR on github? If you have an appropriate license, then you can open a support case? I would suggest to upgrade. There are 2 possibilities - A) it has been fixed in a more recent release and you’’ll get that fix by upgrading. Or B) it remains a bug, you continue to see it, so someone will need to find and fix it, and to get that fix you’ll need to upgrade anyways! If you want to speed up the process, then you will likely need to help a bit. If you do nothing, and nobody else comes up with a better idea, you should not expect anything to change. Are you OK with that? Outside of upgrading, see if you can correlate the breaker messages with anything in your workload, e.g. from any slowlog entries. What trace logging did you enable? In broad terms, what’s your cluster doing, and how loaded is it both on average and at peak load times? Is there anything “custom” added, or is it a vanilla installation?