在Aurora RDS只读副本上进行故障转移，停机时间最少
[英]Fail over on an Aurora RDS read-only replica with minimal downtime
问题描述
I'm wondering what's the best practice to handle the failover of an Aurora RDS Instance. 
我想知道处理Aurora RDS实例的故障转移的最佳实践是什么。 I have a writer instance with two reader instances connected. 我有一个作家实例，并连接了两个读者实例。 The three instances are in three different AZs. 这三个实例位于三个不同的可用区中。
Should I just select my desired instance and click "Failover"? 我应该只选择所需的实例，然后单击“故障转移”吗？ What's the expected downtime? 预期的停机时间是多少？ Can I do this while receiving production traffic? 接收生产流量时可以这样做吗？
2 个解决方案
解决方案1
1 2017-02-26 16:46:38
Failover is in principle instant - the very first thing AWS does is updates the DNS record so it points to the failover instant. 故障转移原则上是即时的-AWS要做的第一件事就是更新DNS记录，使其指向故障转移瞬间。
One thing to be aware of, though, is that a read replica is written to asynchronously, not synchronously, which means it will lag your main database by some level. 但是，需要注意的一件事是，只读副本是异步写入的，而不是同步写入的，这意味着它将在某种程度上落后于您的主数据库。
If you really want to do this whilst recieving production traffic, you in principle can, but you need to make sure any applications will reconnect to the database. 如果您确实想在接收生产流量的同时执行此操作，原则上可以，但是您需要确保所有应用程序都将重新连接到数据库。
解决方案2
0 2017-03-10 18:13:49
Part of the Aurora service is it already had redundancy. Aurora服务的一部分是它已经具有冗余。 Actually redundant redundancy. 实际上是冗余冗余。 If one fails it will take 30 sec. 如果失败，将需要30秒。 for it to switch over to another data center. 它可以切换到另一个数据中心。
https://aws.amazon.com/rds/aurora/ https://aws.amazon.com/rds/aurora/
Amazon Aurora's storage is fault-tolerant and self-healing.
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.