# Running two independent clusters

**URL:** <https://discuss.elastic.co/t/running-two-independent-clusters/17046>\
**Category:** Elasticsearch\
**Created:** [April 16, 2014, 11:45am UTC](https://discuss.elastic.co/t/running-two-independent-clusters/17046 "2014-04-16T11:45:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Steven\_Williamson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steven_williamson/32/1637_2.png) [@Steven\_Williamson](https://discuss.elastic.co/u/Steven_Williamson)\
**Post date:** [April 16, 2014, 11:45am UTC](https://discuss.elastic.co/t/running-two-independent-clusters/17046/1 "2014-04-16T11:45:18Z")

</div>

Hi,

I'm looking at running two ES clusters across two sites. I.e avoid  
clustering across a WAN link, and to provide an environment to test  
upgrades etc.

I'm looking at using RabbitMQ and the RabbitMQ river plugin to stream  
updates to both clusters to keep them in sync.

Is anybody already doing this, and if so do you have details / architecture  
notes to share.

How do you handle seeding the second cluster initially, or bringing it back  
up after a failure mode ?  
How do you ensure the cluster stays consistent during upgrades or  
maintenance etc.  
Any major gotchas to be aware of ?

Any info appreciated as i'd rather not re-invent the wheel from scratch.  
There does not seem to be a generic blueprint for running ES across  
multiple DC's that i can find.

Cheers  
Steve.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/0fc8bc3d-f8fd-4bad-ab63-320b99c17c8c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0fc8bc3d-f8fd-4bad-ab63-320b99c17c8c%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 16, 2014, 11:17pm UTC](https://discuss.elastic.co/t/running-two-independent-clusters/17046/2 "2014-04-16T23:17:07Z")

</div>

Take a look at logstash as the conduit, it should be more than suitable.

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 16 April 2014 21:45, Steven Williamson [steven43126@gmail.com](mailto:steven43126@gmail.com) wrote:

> Hi,
> 
> I'm looking at running two ES clusters across two sites. I.e avoid  
> clustering across a WAN link, and to provide an environment to test  
> upgrades etc.
> 
> I'm looking at using RabbitMQ and the RabbitMQ river plugin to stream  
> updates to both clusters to keep them in sync.
> 
> Is anybody already doing this, and if so do you have details /  
> architecture notes to share.
> 
> How do you handle seeding the second cluster initially, or bringing it  
> back up after a failure mode ?  
> How do you ensure the cluster stays consistent during upgrades or  
> maintenance etc.  
> Any major gotchas to be aware of ?
> 
> Any info appreciated as i'd rather not re-invent the wheel from scratch.  
> There does not seem to be a generic blueprint for running ES across  
> multiple DC's that i can find.
> 
> Cheers  
> Steve.
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/0fc8bc3d-f8fd-4bad-ab63-320b99c17c8c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0fc8bc3d-f8fd-4bad-ab63-320b99c17c8c%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/0fc8bc3d-f8fd-4bad-ab63-320b99c17c8c%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/0fc8bc3d-f8fd-4bad-ab63-320b99c17c8c%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624a\_RHPoFKC70a86mmT%2Bnb1A08XFm0BAbLTWmu32eHh4RQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624a_RHPoFKC70a86mmT%2Bnb1A08XFm0BAbLTWmu32eHh4RQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 1:35am UTC](https://discuss.elastic.co/t/running-two-independent-clusters/17046/3 "2017-07-06T01:35:23Z")

</div>

Closed on July 6, 2017, 1:35am UTC


