在主动被动开放式搜索设置中,在DR期间写入处理
了解 AWS Open Search[1] 的主动被动跨集群复制非常简单。您在主动集群中有一个领导者索引,它将所有内容复制到被动集群中的跟随者索引。如果存在灾难恢复并且我们发现区域故障,我们可以通过被动集群上的追随者索引继续处理读取操作。
但提供的文档并没有经过以下两点。
- 我们如何处理活动集群关闭期间发生的写入操作。是否可以在这段时间内在被动集群上进行写入,并且主集群在恢复联机后会赶上,或者在此期间只能进行读取,并且一旦主动集群恢复,我们需要批量处理所有写入?
- 当主动集群重新上线时,Open Search 是否会自动开始将搜索查询重定向回主动集群而不是被动集群?
此外,如果我们希望测试 Open Search 的 DR 故障转移设置,是否可以模拟活动集群故障并进行测试?
[1] https://docs.aws.amazon.com /opensearch-service/latest/developerguide/replication.html
Understanding Active Passive Cross Cluster replication for AWS Open Search[1] 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
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
您可以采取的一项有效措施是最大限度地利用 SQS(简单队列服务)来存储所有写入。 SQS 允许您将数据保留最多 14 天。一旦写入集群处于活动状态,您就可以继续将 SQS 中保存的数据索引到 Opensearch 中。
One efficient action you can take is to maximize the utilization of SQS (Simple Queue Service) for storing all of your writes. SQS allows you to retain your data for up to 14 days. Once your write cluster is active, you can proceed to index the data preserved in SQS into Opensearch.