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.
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.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.