# Single node takes down entire cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [June 5, 2013, 1:07am UTC](https://discuss.elastic.co/t/single-node-takes-down-entire-cluster/12270 "2013-06-05T01:07:42Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![moj0rising](https://avatars.discourse-cdn.com/v4/letter/m/a5b964/32.png) [@moj0rising](https://discuss.elastic.co/u/moj0rising)\ **Post date:** [June 5, 2013, 1:07am UTC](https://discuss.elastic.co/t/single-node-takes-down-entire-cluster/12270/1 "2013-06-05T01:07:42Z")
Hello, We have a problem where one of our Elastic search nodes runs out of memory and crashes. In the process, the whole (two-node) cluster stops functioning. What can we do to make it so if one node fails, it does not affect the other? All shards are replicated on both nodes. I realize we are probably cutting it too close with regard to memory, which is most likely why the first node goes down -- the index is 8.1 GB and each node has 8 GB RAM. Are there any specific memory requirements for Elastic Search? I've been searching quite a bit and have not been able to find anything on system requirements for the application. I presume having at least as much memory as the index is large would be a good place to start but it would probably be best to know what is proper practise. Thanks for any help you can provide! Mike ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:32am UTC](https://discuss.elastic.co/t/single-node-takes-down-entire-cluster/12270/2 "2017-07-06T02:32:57Z")