# Elastic-search Cluster resizing

**URL:** <https://discuss.elastic.co/t/elastic-search-cluster-resizing/161169>\
**Category:** Elasticsearch\
**Created:** [December 17, 2018, 2:21pm UTC](https://discuss.elastic.co/t/elastic-search-cluster-resizing/161169 "2018-12-17T14:21:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Suhas\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suhas_k/32/31525_2.png) [@Suhas\_K](https://discuss.elastic.co/u/Suhas_K)\
**Post date:** [December 17, 2018, 2:21pm UTC](https://discuss.elastic.co/t/elastic-search-cluster-resizing/161169/1 "2018-12-17T14:21:11Z")

</div>

Hi,

I have a 6 node cluster running in two different servers. I have made some changes in **rackid**.

```auto
cluster.routing.allocation.awareness.attributes: rack_id = Some rackid

```

[About rackid](https://www.elastic.co/guide/en/elasticsearch/reference/current/allocation-awareness.html)

I want to restructure the cluster to 3 nodes. Is there any possibility that I can take backup {snapshot } of current data, which is 6 node cluster and try to import that in 3 node cluster.

**Note:** The data in the 6 node cluster is some where around 1TB.  
Is it possible to get the data backup or i have to forget about the data if consider changing my cluster design form 6 Node to 3 Nodes.

Thanks 🐅

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [December 17, 2018, 2:26pm UTC](https://discuss.elastic.co/t/elastic-search-cluster-resizing/161169/2 "2018-12-17T14:26:32Z")

</div>

> [@Suhas\_K](#):
>
> I want to restructure the cluster to 3 nodes. Is there any possibility that I can take backup {snapshot } of current data, which is 6 node cluster and try to import that in 3 node cluster.

As long as the data still fits and you stay with the same version (or higher) that should not be a problem at all. Elasticsearch does assume all nodes are equal, so if you end up having 2 nodes on one host and one other the other this could cause an imbalance.

---

<div class="post-metadata">

**Author:** ![Suhas\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suhas_k/32/31525_2.png) [@Suhas\_K](https://discuss.elastic.co/u/Suhas_K)\
**Post date:** [December 18, 2018, 5:51am UTC](https://discuss.elastic.co/t/elastic-search-cluster-resizing/161169/3 "2018-12-18T05:51:22Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> As long as the data still fits and you stay with the same version (or higher) that should not be a problem at all. Elasticsearch does assume all n

Thanks for your reply @Christian_Dahlqvist. I think is must start with the snapshot first.  
Regards 🐅

---

<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:** [January 15, 2019, 5:51am UTC](https://discuss.elastic.co/t/elastic-search-cluster-resizing/161169/4 "2019-01-15T05:51:25Z")

</div>

Closed on January 15, 2019, 5:51am UTC

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