如何故障回复到 amazon aurora 全局数据库中的第一个区域
How to fail back to the first region in amazon aurora global database
我在这里关注官方文档
https://aws.amazon.com/getting-started/hands-on/aurora-global-database/
上面写着：
Note: After failover, the newly promoted cluster in Europe (Paris) Region becomes a Regional aurora cluster. Once promoted you cannot add the new DB cluster back to the old Aurora Global Database as a secondary region. If you want to fail back to original region US-East (N. Virginia) or add a secondary cluster in different AWS Region, you need to repeat the steps 6 to 8 by creating a new Aurora Global Database with the newly promoted cluster as the primary cluster. See Failover for Aurora Global Database.
我想知道以下问题：
secondary region的failover基于什么？它是否仅在主要区域关闭时发生？如果我有自定义故障转移策略，那么它是否也可以绑定到 amazon aurora 全局数据库故障转移？
发生failover时，是否自动将secondary region的aurora提升为master？
故障转移后，如果我需要故障回复到主要区域，我能否以某种方式将复制方向从次要区域翻转回主要区域？有没有自动化的方法来做到这一点？
遗憾的是，目前 Aurora 服务本身不执行故障转移（尽管您可以通过 CloudWatch 和 Lambda triggers 自动执行此操作）。
Q: Will Aurora automatically fail over to a secondary region of an Aurora Global Database?
No. If your primary region becomes unavailable, you can manually remove a secondary region from an Aurora Global Database and promote it to take full reads and writes. You will also need to point your application to the newly promoted region.
当发生故障转移时，提升的实例从集群中分离出来，它将成为自己的集群，拥有自己的读写能力。此时集群之间不再有任何关系，您的应用程序将需要重新定位以改为使用此端点。
要回退，您需要在之前的区域中重新创建一个 Aurora 集群（或将数据库更改复制回之前的集群）。更简单的方法可能是创建一个返回原始区域的全局数据库，然后进行故障转移并将您的应用程序重新定位到该区域。
Amazon 最近为全球数据库启用了 write forwarding，因此理论上您可以在故障转移之前将应用程序重新定位回原始区域。
我在这里关注官方文档 https://aws.amazon.com/getting-started/hands-on/aurora-global-database/
上面写着：
Note: After failover, the newly promoted cluster in Europe (Paris) Region becomes a Regional aurora cluster. Once promoted you cannot add the new DB cluster back to the old Aurora Global Database as a secondary region. If you want to fail back to original region US-East (N. Virginia) or add a secondary cluster in different AWS Region, you need to repeat the steps 6 to 8 by creating a new Aurora Global Database with the newly promoted cluster as the primary cluster. See Failover for Aurora Global Database.
我想知道以下问题：
secondary region的failover基于什么？它是否仅在主要区域关闭时发生？如果我有自定义故障转移策略，那么它是否也可以绑定到 amazon aurora 全局数据库故障转移？
发生failover时，是否自动将secondary region的aurora提升为master？
故障转移后，如果我需要故障回复到主要区域，我能否以某种方式将复制方向从次要区域翻转回主要区域？有没有自动化的方法来做到这一点？
遗憾的是，目前 Aurora 服务本身不执行故障转移（尽管您可以通过 CloudWatch 和 Lambda triggers 自动执行此操作）。
Q: Will Aurora automatically fail over to a secondary region of an Aurora Global Database?
No. If your primary region becomes unavailable, you can manually remove a secondary region from an Aurora Global Database and promote it to take full reads and writes. You will also need to point your application to the newly promoted region.
当发生故障转移时，提升的实例从集群中分离出来，它将成为自己的集群，拥有自己的读写能力。此时集群之间不再有任何关系，您的应用程序将需要重新定位以改为使用此端点。
要回退，您需要在之前的区域中重新创建一个 Aurora 集群（或将数据库更改复制回之前的集群）。更简单的方法可能是创建一个返回原始区域的全局数据库，然后进行故障转移并将您的应用程序重新定位到该区域。
Amazon 最近为全球数据库启用了 write forwarding，因此理论上您可以在故障转移之前将应用程序重新定位回原始区域。