# ElasticSearch geo redundancy **URL:** \ **Category:** Elasticsearch\ **Created:** [October 28, 2013, 7:57pm UTC](https://discuss.elastic.co/t/elasticsearch-geo-redundancy/14145 "2013-10-28T19:57:50Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![frosty](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@frosty](https://discuss.elastic.co/u/frosty)\ **Post date:** [October 28, 2013, 7:57pm UTC](https://discuss.elastic.co/t/elasticsearch-geo-redundancy/14145/1 "2013-10-28T19:57:50Z")
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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 28, 2013, 8:15pm UTC](https://discuss.elastic.co/t/elasticsearch-geo-redundancy/14145/2 "2013-10-28T20:15:12Z")
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](http://Elasticsearch.com) @dadoonet | @elasticsearchfr | @scrutmydocs Le 28 oct. 2013 à 20:57, frosty [gopal@avado.com](mailto: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](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Jilles\_van\_Gurp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jilles_van_gurp/32/879_2.png) [@Jilles\_van\_Gurp](https://discuss.elastic.co/u/Jilles_van_Gurp)\ **Post date:** [October 29, 2013, 1:37pm UTC](https://discuss.elastic.co/t/elasticsearch-geo-redundancy/14145/3 "2013-10-29T13:37:23Z")
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. -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:10am UTC](https://discuss.elastic.co/t/elasticsearch-geo-redundancy/14145/4 "2017-07-06T02:10:00Z")