# Log size too large causes kibana to crash

**URL:** <https://discuss.elastic.co/t/log-size-too-large-causes-kibana-to-crash/146417>\
**Category:** Logstash\
**Created:** [August 28, 2018, 8:30pm UTC](https://discuss.elastic.co/t/log-size-too-large-causes-kibana-to-crash/146417 "2018-08-28T20:30:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Derek\_Liu](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@Derek\_Liu](https://discuss.elastic.co/u/Derek_Liu)\
**Post date:** [August 28, 2018, 8:30pm UTC](https://discuss.elastic.co/t/log-size-too-large-causes-kibana-to-crash/146417/1 "2018-08-28T20:30:55Z")

</div>

I am using packetbeat to monitor search queries and results on elasticsearch, then use logstash to send it to elasticsearch. Because the result of each search is too large, everytime when I try to load the logstash-\* indexer on kibana crashes.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [August 28, 2018, 9:02pm UTC](https://discuss.elastic.co/t/log-size-too-large-causes-kibana-to-crash/146417/2 "2018-08-28T21:02:42Z")

</div>

Could you describe exactly what you mean, e.g. by providing a screenshot or error message? Does the server-side Kibana service crash? Or the browser?

---

<div class="post-metadata">

**Author:** ![Derek\_Liu](https://avatars.discourse-cdn.com/v4/letter/d/7ab992/32.png) [@Derek\_Liu](https://discuss.elastic.co/u/Derek_Liu)\
**Post date:** [August 28, 2018, 9:12pm UTC](https://discuss.elastic.co/t/log-size-too-large-causes-kibana-to-crash/146417/3 "2018-08-28T21:12:28Z")

</div>

![10%20PM](https://us1.discourse-cdn.com/elastic/original/3X/2/4/2491b466ab6a65252942b37b38ff7039005d213c.png) ![21%20PM](https://us1.discourse-cdn.com/elastic/original/3X/5/2/52bc50a0891679e3c8b7a570b4fd5e8a2fe34977.png)

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [August 29, 2018, 9:27am UTC](https://discuss.elastic.co/t/log-size-too-large-causes-kibana-to-crash/146417/4 "2018-08-29T09:27:12Z")

</div>

Your Elasticsearch cluster is in bad shape. Its logs should contain clues.

---

<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:** [September 26, 2018, 9:27am UTC](https://discuss.elastic.co/t/log-size-too-large-causes-kibana-to-crash/146417/5 "2018-09-26T09:27:15Z")

</div>

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