# Elasticsearch service stops rapidly

**URL:** <https://discuss.elastic.co/t/elasticsearch-service-stops-rapidly/67492>\
**Category:** Elasticsearch\
**Created:** [November 29, 2016, 2:01pm UTC](https://discuss.elastic.co/t/elasticsearch-service-stops-rapidly/67492 "2016-11-29T14:01:52Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![munam-nauman](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@munam-nauman](https://discuss.elastic.co/u/munam-nauman)\
**Post date:** [November 29, 2016, 2:01pm UTC](https://discuss.elastic.co/t/elasticsearch-service-stops-rapidly/67492/1 "2016-11-29T14:01:52Z")

</div>

Hello. My elasticsearch engine stops after every 5-6 hours and I had to restart it again. Can anyone please help me. I am running elasticsearch server in CentOS 7.

Thanks in anticipation.

---

<div class="post-metadata">

**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\
**Post date:** [November 29, 2016, 2:11pm UTC](https://discuss.elastic.co/t/elasticsearch-service-stops-rapidly/67492/2 "2016-11-29T14:11:52Z")

</div>

have you checked what the logs say? What is your heap size, what is the total memory of your system  
Also double check your /var/log/messages see if there is information there too

---

<div class="post-metadata">

**Author:** ![munam-nauman](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@munam-nauman](https://discuss.elastic.co/u/munam-nauman)\
**Post date:** [November 30, 2016, 6:42am UTC](https://discuss.elastic.co/t/elasticsearch-service-stops-rapidly/67492/3 "2016-11-30T06:42:44Z")

</div>

yes you are right. In log/messages it is giving me error. "Out of Memory Kill process or sacrifice child". Should I increase physical memory of my server ? Can you help me please ? Total physical memory of my server is 2GB.

---

<div class="post-metadata">

**Author:** ![danielgc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielgc/32/13501_2.png) [@danielgc](https://discuss.elastic.co/u/danielgc)\
**Post date:** [November 30, 2016, 3:04pm UTC](https://discuss.elastic.co/t/elasticsearch-service-stops-rapidly/67492/4 "2016-11-30T15:04:30Z")

</div>

I'm very interested on this topic because I'm experiencing the same problem ☹

---

<div class="post-metadata">

**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\
**Post date:** [December 1, 2016, 12:29am UTC](https://discuss.elastic.co/t/elasticsearch-service-stops-rapidly/67492/5 "2016-12-01T00:29:24Z")

</div>

well there are a couple ways to deal with this

1. yes you can add more memory to your system and take a look at java new memory model they changed it. but what is yourHeap size set to?

2. if your using all your heap you might want to spawn more instances to reduce the work load on any one server this will help performance and should lower some heap usage

3. for optimal speed you need much more memory then your heap requires so linux can cache disk data in memory. linux will if you have enough will cache the entire index in memory. nothing is faster then cached data. the only exception to this is if your data updates often

---

<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:** [December 29, 2016, 12:29am UTC](https://discuss.elastic.co/t/elasticsearch-service-stops-rapidly/67492/6 "2016-12-29T00:29:25Z")

</div>

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