Running two independent clusters


(Steven Williamson) #1

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0fc8bc3d-f8fd-4bad-ab63-320b99c17c8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Mark Walkom) #2

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
web: www.campaignmonitor.com

On 16 April 2014 21:45, Steven Williamson 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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/0fc8bc3d-f8fd-4bad-ab63-320b99c17c8c%40googlegroups.comhttps://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.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624a_RHPoFKC70a86mmT%2Bnb1A08XFm0BAbLTWmu32eHh4RQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(system) #3