# Kibana : internal server error

**URL:** <https://discuss.elastic.co/t/kibana-internal-server-error/267790>\
**Category:** Kibana\
**Created:** [March 19, 2021, 10:00am UTC](https://discuss.elastic.co/t/kibana-internal-server-error/267790 "2021-03-19T10:00:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![poff](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/poff/32/81795_2.png) [@poff](https://discuss.elastic.co/u/poff)\
**Post date:** [March 19, 2021, 4:07pm UTC](https://discuss.elastic.co/t/kibana-internal-server-error/267790/2 "2021-03-19T16:07:32Z")

</div>

Hey there! From that top line in the error log you pasted, it's looking like you're hitting a circuit breaker that prevents the instance from running into an out of memory exception.

Looks like someone on the forums hit something similar to this: [What does this error mean - Data too large, data for [\<transport\_request\>]](https://discuss.elastic.co/t/what-does-this-error-mean-data-too-large-data-for-transport-request/209345)  
Here's more info on the circuit breaker if you're curious: [Improve Elasticsearch resiliency with the real memory circuit breaker | Elastic Blog](https://www.elastic.co/blog/improving-node-resiliency-with-the-real-memory-circuit-breaker)

It seems like a good fix here would be to increase the amount of heap memory that your kibana instance is using so you're able to retrieve that data

---

_[View the full topic](https://discuss.elastic.co/t/kibana-internal-server-error/267790)._