Open Search Cross Cluster Replication
Understanding Active Passive Cross Cluster replication for AWS Open Search1 is pretty straightforward. You have a leader index in the active cluster that replicates everything to the follower index in the passive cluster. In case there is a DR and we witness a region failure, we can continue to process read operations through the follower index on the passive cluster.
However, the documentation provided does not go through the following two points.
How do we handle write operations that come during the time the active cluster is down. Is it possible to write on the passive cluster during this time and the primary would catch up when it comes back online or only read is possible during this time, and we need to batch process all the writes once active cluster comes back up ?
When active cluster comes back online, does Open Search automatically starts redirecting search queries back to active cluster instead of the passive cluster ?
In addition, in case we wish to test the DR failover setup for Open Search, is it possible to simulate active cluster failure and test ?
1 https://docs.aws.amazon.com/opensearch-service/latest/developerguide/replication.html
Hi. That's a great question. Below is the clarification :
- Currently, replication under OpenSearch works in active-passive model. The follower will not take any write traffic and is only open for search. Yes, once the leader cluster is back online, the writes have to be made on the leader(/active) cluster.
- Each cluster (leader and follower) will have separate endpoint and OpenSearch doesn't redirect the search traffic. Search traffic will continue on the configured search endpoint at the client.
- Inducing failure directly on the managed service nodes is not possible. Please follow the steps for the failover onto the follower cluster: Terminate the connection between follower and leader cluster (Connection APIs) Trigger stop on all the follower indices that were getting replication: https://opensearch.org/docs/latest/replication-plugin/get-started/#stop-replication Once replication is stopped on all the indices, the follower indices should be able to take write traffic.
Let us know, If you have any further questions.
Relevant questions
Open Search Cross Cluster Replication
asked 2 months agoBest practices for faster seeding of cross-region replica Aurora cluster to enable failback
Accepted Answer"Create Aurora Read Replica" option not available to migrate from RDS Postgres 11.12 to Aurora 11.12.
asked 2 months agoCross-Region Replicas - can't replicate views or procedures
asked 3 years agoOpenSearch cross-cluster search and autotune
asked 3 months agoUpgrading Aurora MySQL 5.6 to 5.7 on cross region replica stuck in pre-upgrade checks and reboots every 30 minutes
asked 2 months agoHow to enable Logical Replication for existing Aurora PG 13 Cluster?
asked 6 months agoSSL replication between Aurora clusters
Accepted Answerasked 3 years agoAurora Create cross-region read replica vs Add Region
Accepted Answerasked a year agoEFS Replication across accounts
asked a month ago
Thanks for your help Varun.