# Migrating Elasticsearch node

**URL:** <https://discuss.elastic.co/t/migrating-elasticsearch-node/62091>\
**Category:** Elasticsearch\
**Created:** [October 3, 2016, 4:25pm UTC](https://discuss.elastic.co/t/migrating-elasticsearch-node/62091 "2016-10-03T16:25:09Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![sarveshdamle](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@sarveshdamle](https://discuss.elastic.co/u/sarveshdamle)\
**Post date:** [October 3, 2016, 4:25pm UTC](https://discuss.elastic.co/t/migrating-elasticsearch-node/62091/1 "2016-10-03T16:25:09Z")

</div>

Are there any special consideration for migrating elasticsearch nodes?

OS: CentOS  
Old ES Version: 2.1.0  
Old ES Cluster: 3 servers (5 shards each with 1 replica)  
Old topology:  
Server1 Node: master=true, data=true (only 1 node)  
Server2 Node: master=true, data=true (only 1 node)  
Server3 Node: master=false, data=true (only 1 node)

New ES Version: 2.4.0  
New Topology:  
Server1 Node: master=true, data=false | master=false, data=true (2 nodes)  
Server2 Node: master=true, data=false | master=false, data=true (2 nodes)  
Server3 Node: master=flase, data=false | master=false, data=true (2 nodes)

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [October 3, 2016, 7:45pm UTC](https://discuss.elastic.co/t/migrating-elasticsearch-node/62091/2 "2016-10-03T19:45:11Z")

</div>

Are you going to perform an online migration? You'll want to use the same JVM version on all machines that are part of the same cluster. You should also keep in mind that shards won't move from a newer version of ES to an older. Finally, are you aware that a cluster with two master-eligible nodes will either not be fault tolerant (i.e. won't survive if one of the masters goes down) or will be susceptible to split brain situations? It seems people want to implement master-only nodes far more than what is warranted.

---

<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 3, 2016, 8:07pm UTC](https://discuss.elastic.co/t/migrating-elasticsearch-node/62091/3 "2016-10-03T20:07:31Z")

</div>

You'd be better off having 3 master nodes - [https://www.elastic.co/guide/en/elasticsearch/guide/current/important-configuration-changes.html#\_minimum\_master\_nodes](https://www.elastic.co/guide/en/elasticsearch/guide/current/important-configuration-changes.html#_minimum_master_nodes)

---

<div class="post-metadata">

**Author:** ![sarveshdamle](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@sarveshdamle](https://discuss.elastic.co/u/sarveshdamle)\
**Post date:** [October 3, 2016, 8:16pm UTC](https://discuss.elastic.co/t/migrating-elasticsearch-node/62091/4 "2016-10-03T20:16:39Z")

</div>

I am planning inline migration. I was planning the new master nodes pointing to the same "data" folder. Thus the follow up question.

What about the data folder?  
Can the same data folder be used?  
Once we have the new "data-nodes" (with the new data folder) will the data be spread across them seamlessly?

---

<div class="post-metadata">

**Author:** ![sarveshdamle](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@sarveshdamle](https://discuss.elastic.co/u/sarveshdamle)\
**Post date:** [October 3, 2016, 8:17pm UTC](https://discuss.elastic.co/t/migrating-elasticsearch-node/62091/5 "2016-10-03T20:17:14Z")

</div>

Ok. I will make three master nodes. Thanks for pointing out.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [October 4, 2016, 5:32am UTC](https://discuss.elastic.co/t/migrating-elasticsearch-node/62091/6 "2016-10-04T05:32:41Z")

</div>

> Can the same data folder be used?

No.

> Once we have the new "data-nodes" (with the new data folder) will the data be spread across them seamlessly?

Yes, the shards will be distributed evenly. If your shards have roughly the same size you'll have roughly the same amount of data on each node.

---

<div class="post-metadata">

**Author:** ![sarveshdamle](https://avatars.discourse-cdn.com/v4/letter/s/df788c/32.png) [@sarveshdamle](https://discuss.elastic.co/u/sarveshdamle)\
**Post date:** [October 4, 2016, 3:34pm UTC](https://discuss.elastic.co/t/migrating-elasticsearch-node/62091/7 "2016-10-04T15:34:35Z")

</div>

Does the master node node need more memory or does the data node need more memory?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [October 4, 2016, 5:39pm UTC](https://discuss.elastic.co/t/migrating-elasticsearch-node/62091/8 "2016-10-04T17:39:54Z")

</div>

The role of being a master in a small cluster doesn't require much in terms of resources.

---

<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:15pm UTC](https://discuss.elastic.co/t/migrating-elasticsearch-node/62091/9 "2017-07-05T22:15:02Z")

</div>


