# Adding new DATA Node on existing Cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [January 2, 2020, 3:13pm UTC](https://discuss.elastic.co/t/adding-new-data-node-on-existing-cluster/213592 "2020-01-02T15:13:21Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Emanuil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/emanuil/32/36783_2.png) [@Emanuil](https://discuss.elastic.co/u/Emanuil)\ **Post date:** [January 8, 2020, 2:59pm UTC](https://discuss.elastic.co/t/adding-new-data-node-on-existing-cluster/213592/4 "2020-01-08T14:59:07Z")
I'd generally recommend keeping one cluster per data centre and using [Cross-Cluster Search](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cross-cluster-search.html) . There is also some commercial functionality around this in the form of [Cross Cluster Replication](https://www.elastic.co/guide/en/elasticsearch/reference/current/xpack-ccr.html). Don't you find latency between the nodes is too much of a problem when each node is in a separate data center? I would still make sure there are 3 nodes. The problem with 2 is that you get no redundancy - if one goes down the entire cluster **should** go down. If it's not configured to do that, 2 nodes has the potential for a split brain problem, see [this discuss question for info, especially this answer](https://discuss.elastic.co/t/need-more-clarity-and-understanding-on-split-brain-problem/53184/6) on what to do with 2 nodes. So this is why I would add at least one more node - then one of them can go down and the cluster keep running with 2 out of 3. Overall I definitely wouldn't recommend running a cluster across 2 data centers, the nodes talk _a lot_ between themselves when you're adding data or if a node fails. Unless the 2 centers are right next to each other, you're going to run into serious trouble as you put load on the cluster. --- _[View the full topic](https://discuss.elastic.co/t/adding-new-data-node-on-existing-cluster/213592)._