# Elasticsearch node stopped itself **URL:** \ **Category:** Elasticsearch\ **Created:** [February 27, 2017, 10:52am UTC](https://discuss.elastic.co/t/elasticsearch-node-stopped-itself/76605 "2017-02-27T10:52:36Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Balamurali](https://avatars.discourse-cdn.com/v4/letter/b/90db22/32.png) [@Balamurali](https://discuss.elastic.co/u/Balamurali)\ **Post date:** [February 27, 2017, 10:52am UTC](https://discuss.elastic.co/t/elasticsearch-node-stopped-itself/76605/1 "2017-02-27T10:52:36Z")
Hi all, we are using ES 1.37 cluster with four data nodes , 2 master nodes with 4 GB JVM. **Within Three days, particular node stopped itself thrice .but there is no messages (stopped or error messages ) in log.** what is happening behind , how to resolve this issue. can anyone help us!!! ---
**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:** [February 27, 2017, 3:07pm UTC](https://discuss.elastic.co/t/elasticsearch-node-stopped-itself/76605/2 "2017-02-27T15:07:05Z")
Hey, first, do not run such an old version. Second, if there are no messages in the log file (a log file excerpt would have been nice), then maybe the kernel OOM killer has killed that process? You could check that using `dmesg`. If thats not the case, you should check your log files again. --Alex ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 27, 2017, 3:07pm UTC](https://discuss.elastic.co/t/elasticsearch-node-stopped-itself/76605/3 "2017-03-27T15:07:10Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.