# How to stop auto-relocation?

**URL:** <https://discuss.elastic.co/t/how-to-stop-auto-relocation/64401>\
**Category:** Elasticsearch\
**Created:** [October 31, 2016, 4:45am UTC](https://discuss.elastic.co/t/how-to-stop-auto-relocation/64401 "2016-10-31T04:45:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eugene\_Gwon](https://avatars.discourse-cdn.com/v4/letter/e/6a8cbe/32.png) [@Eugene\_Gwon](https://discuss.elastic.co/u/Eugene_Gwon)\
**Post date:** [October 31, 2016, 4:45am UTC](https://discuss.elastic.co/t/how-to-stop-auto-relocation/64401/1 "2016-10-31T04:45:51Z")

</div>

Hello all,  
I'm using 3 nodes of ES 1.7.4 with Graylog2-1.3.  
currently, one of ES node is a master, and 2 nodes are data node. and these nodes have 8GB of ram on each server.

and here's the problem : If I querying too big data, then one of data node crashes with OOM.  
after than, master node automatically relocate shards and replicas.  
but in most time, I can restart elasticsearch in very short time, so It seems doesn't need to relocate shard.

Is there anyway to stop auto-relocation some amount of time?  
If I can stop it about 10~20 mins, It would be great.

Thanks.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 31, 2016, 5:06am UTC](https://discuss.elastic.co/t/how-to-stop-auto-relocation/64401/2 "2016-10-31T05:06:34Z")

</div>

You can adopt the process here - [https://www.elastic.co/guide/en/elasticsearch/reference/1.7/setup-upgrade.html#rolling-upgrades](https://www.elastic.co/guide/en/elasticsearch/reference/1.7/setup-upgrade.html#rolling-upgrades)

But you can't do that as a node goes down, it has to be before or as soon as you realise it's gone.

---

<div class="post-metadata">

**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\
**Post date:** [October 31, 2016, 9:00am UTC](https://discuss.elastic.co/t/how-to-stop-auto-relocation/64401/3 "2016-10-31T09:00:10Z")

</div>

Delayed allocation (see [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/delayed-allocation.html)) will help you.

---

<div class="post-metadata">

**Author:** ![Eugene\_Gwon](https://avatars.discourse-cdn.com/v4/letter/e/6a8cbe/32.png) [@Eugene\_Gwon](https://discuss.elastic.co/u/Eugene_Gwon)\
**Post date:** [November 1, 2016, 6:50am UTC](https://discuss.elastic.co/t/how-to-stop-auto-relocation/64401/4 "2016-11-01T06:50:02Z")

</div>

After some test and 'little' frustrating situation, I decided to respect the nature of ElasticSearch and take peace of mind.  
Thanks for all your response 🙂

---

<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:** [July 5, 2017, 10:07pm UTC](https://discuss.elastic.co/t/how-to-stop-auto-relocation/64401/5 "2017-07-05T22:07:59Z")

</div>