# Cluster expansion

**URL:** https://discuss.elastic.co/t/cluster-expansion/145886
**Category:** Elasticsearch
**Created:** [August 24, 2018, 10:22am UTC](https://discuss.elastic.co/t/cluster-expansion/145886 "2018-08-24T10:22:54Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Tuckson](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@Tuckson](https://discuss.elastic.co/u/Tuckson)
#### Post date: [August 24, 2018, 10:22am UTC](https://discuss.elastic.co/t/cluster-expansion/145886/1 "2018-08-24T10:22:54Z")

</div>

Hi,

Until now we had an elk stack consisting of 2 servers, 1 kibana/logstash and 1 with elastichsearch on it.  
Since we expect our data to multiply, I would like to expand the single ES node to a cluster. So I got 5 extra vm's with enough resources, installed ES on it and am puzzling now what to do.

I can find a lot on moving to a new cluster, but actually this is a live system and I want the current node to stay the node which is contacted by logstash and kibana.

Please correct me if doing something stupid, but what I had in mind was this:  
New servers become ES datanodes.  
Current server becomes client/master node (I can combine these in 1 node, right?)

Now my question is how I can I make the current data available on the new servers and then have it function the way I want it? Or is it strongly advised to take another approach?

Thnx

---

<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: [September 21, 2018, 10:22am UTC](https://discuss.elastic.co/t/cluster-expansion/145886/2 "2018-09-21T10:22:56Z")

</div>

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