# "Wide" cluster

**URL:** https://discuss.elastic.co/t/wide-cluster/137603
**Category:** Elasticsearch
**Created:** [June 27, 2018, 11:09am UTC](https://discuss.elastic.co/t/wide-cluster/137603 "2018-06-27T11:09:59Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![LesioS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lesios/32/32364_2.png) [@LesioS](https://discuss.elastic.co/u/LesioS)
#### Post date: [June 27, 2018, 11:10am UTC](https://discuss.elastic.co/t/wide-cluster/137603/1 "2018-06-27T11:10:00Z")

</div>

I wonder if multinode cluster has any limitations with geographical localization of nodes (mainly master). Is it possible (and efficient) to install 3 master nodes in e.g London, NY and Sydney respectively and connect them to 1 cluster? Is it any limitations for such approach, e.g in licenses or something else?  
Also add to it several data nodes - is it important where they are? I think that they should be "close" to master node but I'd like to be sure.

regards,  
Lechu

---

<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: [June 27, 2018, 11:14am UTC](https://discuss.elastic.co/t/wide-cluster/137603/2 "2018-06-27T11:14:47Z")

</div>

Nodes in an Elasticsearch requires low latencies and good throughput between the nodes, so deploying clusters distributed across regions in that way is not supported and likely to cause all sorts of problems.

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [June 27, 2018, 11:21am UTC](https://discuss.elastic.co/t/wide-cluster/137603/3 "2018-06-27T11:21:46Z")

</div>

Adding to this that we are working on Cross Data Center Replication so we will support such a thing in the future.

---

<div class="post-metadata">

### Author: ![LesioS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lesios/32/32364_2.png) [@LesioS](https://discuss.elastic.co/u/LesioS)
#### Post date: [June 27, 2018, 11:22am UTC](https://discuss.elastic.co/t/wide-cluster/137603/4 "2018-06-27T11:22:18Z")

</div>

So, it's possible but highly unrecommended? No obstacles to do that?

---

<div class="post-metadata">

### Author: ![LesioS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lesios/32/32364_2.png) [@LesioS](https://discuss.elastic.co/u/LesioS)
#### Post date: [June 27, 2018, 11:23am UTC](https://discuss.elastic.co/t/wide-cluster/137603/5 "2018-06-27T11:23:02Z")

</div>

And "the future" means?....

---

<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: [June 27, 2018, 11:27am UTC](https://discuss.elastic.co/t/wide-cluster/137603/6 "2018-06-27T11:27:55Z")

</div>

What is the use-case? What are you looking to achieve with this set-up?

---

<div class="post-metadata">

### Author: ![LesioS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lesios/32/32364_2.png) [@LesioS](https://discuss.elastic.co/u/LesioS)
#### Post date: [June 27, 2018, 11:30am UTC](https://discuss.elastic.co/t/wide-cluster/137603/7 "2018-06-27T11:30:15Z")

</div>

1 cluster for customers spread all over the world....

---

<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: [June 27, 2018, 11:31am UTC](https://discuss.elastic.co/t/wide-cluster/137603/8 "2018-06-27T11:31:25Z")

</div>

Can you describe the use-case? Is it read-heavy? Is it write-heavy? What data volumes are we talking about? Will all regions hold a copy of all data?

---

<div class="post-metadata">

### Author: ![LesioS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lesios/32/32364_2.png) [@LesioS](https://discuss.elastic.co/u/LesioS)
#### Post date: [June 27, 2018, 12:06pm UTC](https://discuss.elastic.co/t/wide-cluster/137603/9 "2018-06-27T12:06:01Z")

</div>

Now it's only theoretical question: is it possible or not. Looking in your answers: yes. Right?

---

<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: [June 27, 2018, 12:09pm UTC](https://discuss.elastic.co/t/wide-cluster/137603/10 "2018-06-27T12:09:28Z")

</div>

Possible? Maybe in theory. In reality it is however definitely not recommended as you are likely to suffer from cluster instability and poor performance.

---

<div class="post-metadata">

### Author: ![LesioS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lesios/32/32364_2.png) [@LesioS](https://discuss.elastic.co/u/LesioS)
#### Post date: [June 27, 2018, 12:16pm UTC](https://discuss.elastic.co/t/wide-cluster/137603/11 "2018-06-27T12:16:09Z")

</div>

Good to know - thanks

---

<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 25, 2018, 12:27pm UTC](https://discuss.elastic.co/t/wide-cluster/137603/12 "2018-07-25T12:27:06Z")

</div>

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