Does ElasticSearch support multiple data center deployment with geo
redundancy? I'm looking for active/active (preferred). If it is not
supported, I'm thinking of two parallel deployments (one in each DC) and
ingest the same data into both. I'll need to build logic in the client tier
to handle geo failure here.
Does Elasticsearch support multiple data center deployment with geo redundancy? I'm looking for active/active (preferred). If it is not supported, I'm thinking of two parallel deployments (one in each DC) and ingest the same data into both. I'll need to build logic in the client tier to handle geo failure here.
On Monday, October 28, 2013 8:57:50 PM UTC+1, frosty wrote:
Does Elasticsearch support multiple data center deployment with geo
redundancy? I'm looking for active/active (preferred). If it is not
supported, I'm thinking of two parallel deployments (one in each DC) and
ingest the same data into both. I'll need to build logic in the client tier
to handle geo failure here.
Not currently. There will be a snapshot/restore style functionality in
version 1.0, which might be a first step towards a cluster 2 cluster style
replication. Otherwise, I'd recommend using e.g. couchdb as your
replicating datastore and have Elasticsearch clusters index from that.
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.