# High Availability with 2 DCs **URL:** \ **Category:** Elasticsearch\ **Tags:** ccr-cross-cluster-replication\ **Created:** [July 22, 2020, 9:18am UTC](https://discuss.elastic.co/t/high-availability-with-2-dcs/242159 "2020-07-22T09:18:37Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Muttley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/muttley/32/72586_2.png) [@Muttley](https://discuss.elastic.co/u/Muttley)\ **Post date:** [July 22, 2020, 9:18am UTC](https://discuss.elastic.co/t/high-availability-with-2-dcs/242159/1 "2020-07-22T09:18:38Z")
Hi, I am setting up a cluster (or two) The plan is to have nodes in the US and in EU Looking through posts regarding HA I can see 3 ways this is implemented 1. Two clusters, logstash sends to Cluster A, Cluster B uses CCR to pull a copy of all the data. Failover involves reconfiguring logstash and cluster B to be primary. 2. One cluster with zoning to ensure at least one replica in each DC. Logstash could be configured to write to all nodes. Failover would be fully automatic. 3. Two separate clusters with logstash configured to write to both clusters. I read a post that implied logstash would stall in this scenario when the primary goes down. [Multiple ELK cluster output](https://discuss.elastic.co/t/multiple-elk-cluster-output/175810) All these solutions seem to offer an RPO of zero option 2 with a RTO of zero also. Does a geographically distributed cluster affect performance ? What is the benefit of CCR as opposed to zoning? Any factors I am not considering? Many thanks in advance. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [July 22, 2020, 9:31am UTC](https://discuss.elastic.co/t/high-availability-with-2-dcs/242159/2 "2020-07-22T09:31:36Z")
Option 2 is not supported so go with option 1 or 3. For option 3 it often helps adding a message queue like Kafka and have 2 Logstash instances each read from this and write to one cluster. This allows Kafka to buffer if one cluster is unavailable. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 19, 2020, 9:31am UTC](https://discuss.elastic.co/t/high-availability-with-2-dcs/242159/3 "2020-08-19T09:31:39Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.