# Kibana and Elasticsearch Keep crashing **URL:** \ **Category:** Kibana\ **Created:** [October 12, 2016, 3:21pm UTC](https://discuss.elastic.co/t/kibana-and-elasticsearch-keep-crashing/62826 "2016-10-12T15:21:33Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [October 14, 2016, 12:29pm UTC](https://discuss.elastic.co/t/kibana-and-elasticsearch-keep-crashing/62826/7 "2016-10-14T12:29:27Z")
If you read that log, you can spot an out of memory exception. This means you have to restart your node immediately, as the behaviour after such an exception is not specified (you just dont know if everything works or not). However in order to prevent those issues in the future, you should find out what triggers this exception. Is it a special query? You might want to read the following docs regarding to that topic > **[Limiting Memory Usage | Elasticsearch: The Definitive Guide \[2.x\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/guide/current/_limiting_memory_usage.html)** > **[Heap: Sizing and Swapping | Elasticsearch: The Definitive Guide \[2.x\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html)** > **[Six Ways to Crash Elasticsearch](https://www.elastic.co/blog/found-crash-elasticsearch)** > > As much as we love Elasticsearch, at Found we've seen customers crash their clusters in numerous ways. Mostly due to simple misunderstandings and usually the fixes are fairly straightforward. In our quest to enlighten new adopters and entertain the... > [@Getting OOME's (Out of Memory Exceptions) to stop](https://discuss.elastic.co/t/getting-oomes-out-of-memory-exceptions-to-stop/18332): > > I have a 10 machine cluster where frequently (about once per day when indexing and querying is at its height) one elasticsearch node goes OOM... It usually recovers, but by this time the cluster is redistributing the lost shards, which causes more load, which often in turn causes an OOM on another machine. Each machine has 32GB memory of which I currently have 12GB allocated to Elasticsearch. I have logstash (max 500M) and redis (max 2GB) running on the machines too, and see that the rem… You can use the cat APIs or monitoring to see if you have continously rising memory usages or spikes which cause this behaviour. Hope this helps. --Alex --- _[View the full topic](https://discuss.elastic.co/t/kibana-and-elasticsearch-keep-crashing/62826)._