# Geo-distributed cluster

**URL:** <https://discuss.elastic.co/t/geo-distributed-cluster/6771>\
**Category:** Elasticsearch\
**Created:** [February 21, 2012, 3:10pm UTC](https://discuss.elastic.co/t/geo-distributed-cluster/6771 "2012-02-21T15:10:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeangld](https://avatars.discourse-cdn.com/v4/letter/j/4af34b/32.png) [@jeangld](https://discuss.elastic.co/u/jeangld)\
**Post date:** [February 21, 2012, 3:10pm UTC](https://discuss.elastic.co/t/geo-distributed-cluster/6771/1 "2012-02-21T15:10:49Z")

</div>

Hi,

I was able to set up my local mini cluster and ES is finding the  
nearby machines in my local network and redistributes the data  
according to my settings. I've also read about the Amazon EC2  
instances, but I'm thinking about following situation:

I have 2 dedicated servers in Europe, two in USA and two in Asia. I  
plan to distribute my ES index to those locations. If I set my  
replicas to 2, I intend to end up wit a copy in each location. So, the  
two servers in each location distribute the load, and in every  
continent a full copy is available. If one server (in USA) goes down,  
ES would find the necessary data (with a higher network latency)  
either in Europe or in Asia.

Is it possible to configure ES in such a way, that I set the 6 IP  
adresses of each server in a config file and it knows how to  
distribute accordingly? From what I've read when I searched this was  
planned in some future version, but I don't know how current this  
information is.

Thanks,

Jean

---

<div class="post-metadata">

**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\
**Post date:** [February 22, 2012, 4:55am UTC](https://discuss.elastic.co/t/geo-distributed-cluster/6771/2 "2012-02-22T04:55:37Z")

</div>

Jean,

Look up Allocation Awareness on ES site + the thread I started on that  
topic on the ML recently.

## Otis

Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html)  
Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html)

On Feb 21, 10:10 am, "[jean...@yahoo.com](mailto:jean...@yahoo.com)" [jean...@yahoo.com](mailto:jean...@yahoo.com) wrote:

> Hi,
> 
> I was able to set up my local mini cluster and ES is finding the  
> nearby machines in my local network and redistributes the data  
> according to my settings. I've also read about the Amazon EC2  
> instances, but I'm thinking about following situation:
> 
> I have 2 dedicated servers in Europe, two in USA and two in Asia. I  
> plan to distribute my ES index to those locations. If I set my  
> replicas to 2, I intend to end up wit a copy in each location. So, the  
> two servers in each location distribute the load, and in every  
> continent a full copy is available. If one server (in USA) goes down,  
> ES would find the necessary data (with a higher network latency)  
> either in Europe or in Asia.
> 
> Is it possible to configure ES in such a way, that I set the 6 IP  
> adresses of each server in a config file and it knows how to  
> distribute accordingly? From what I've read when I searched this was  
> planned in some future version, but I don't know how current this  
> information is.
> 
> Thanks,
> 
> Jean

---

<div class="post-metadata">

**Author:** ![Berkay\_Mollamustafao](https://avatars.discourse-cdn.com/v4/letter/b/22d042/32.png) [@Berkay\_Mollamustafao](https://discuss.elastic.co/u/Berkay_Mollamustafao)\
**Post date:** [February 22, 2012, 5:14am UTC](https://discuss.elastic.co/t/geo-distributed-cluster/6771/3 "2012-02-22T05:14:18Z")

</div>

I think having a cluster distributed across data centers is not a good  
idea. One of the most problematic things that can happen with ES is when  
the nodes loose communication with each other, what is referred to as  
"split brain". It's a lot more likely to have connectivity issues when  
cluster spans across data centers. Latency may also cause potential  
performance problems  
You'd be better off to have a separate cluster at each data center and use  
the application layer to index the data at each cluster, rather than  
relying on ES to replicate the data.

My 3.1415 cents ...

Regards,  
Berkay Mollamustafaoglu  
mberkay on yahoo, google and skype

On Tue, Feb 21, 2012 at 10:10 AM, [jeangld@yahoo.com](mailto:jeangld@yahoo.com) [jeangld@yahoo.com](mailto:jeangld@yahoo.com)wrote:

> Hi,
> 
> I was able to set up my local mini cluster and ES is finding the  
> nearby machines in my local network and redistributes the data  
> according to my settings. I've also read about the Amazon EC2  
> instances, but I'm thinking about following situation:
> 
> I have 2 dedicated servers in Europe, two in USA and two in Asia. I  
> plan to distribute my ES index to those locations. If I set my  
> replicas to 2, I intend to end up wit a copy in each location. So, the  
> two servers in each location distribute the load, and in every  
> continent a full copy is available. If one server (in USA) goes down,  
> ES would find the necessary data (with a higher network latency)  
> either in Europe or in Asia.
> 
> Is it possible to configure ES in such a way, that I set the 6 IP  
> adresses of each server in a config file and it knows how to  
> distribute accordingly? From what I've read when I searched this was  
> planned in some future version, but I don't know how current this  
> information is.
> 
> Thanks,
> 
> Jean

---

<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 6, 2017, 3:38am UTC](https://discuss.elastic.co/t/geo-distributed-cluster/6771/4 "2017-07-06T03:38:36Z")

</div>


