ElasticSearch geo redundancy


(frosty) #1

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.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.


(David Pilato) #2

Right now, I would recommend to manage that on the client level as you suggested, mostly for network latency reasons.

My 2 cents

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 28 oct. 2013 à 20:57, frosty gopal@avado.com a écrit :

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.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.


(Jilles van Gurp) #3

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 elastic search clusters index from that.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #4