实现 Redshift 的高可用性？
[英]Achieving High Availability for Redshift?
问题描述
It is my understanding that Redshift is built for performance but not for Availability.
据我了解，Redshift 是为性能而不是可用性而构建的。 The documentation https://aws.amazon.com/redshift/faqs/ suggest that once any node is down, the whole cluster is down until the node is restored.文档https://aws.amazon.com/redshift/faqs/建议一旦任何节点宕机，整个集群就会宕机，直到该节点恢复。 In the case of the AZ failure, you have no luck at all.在 AZ 失败的情况下，你一点运气都没有。
This post suggests having a double cluster https://aws.amazon.com/blogs/big-data/building-multi-az-or-multi-region-amazon-redshift-clusters/ however, it is not clear to me how do you replicate Looker's PDT tables to support instant failover via Route 53 to the standby cluster?这篇文章建议有一个双集群https://aws.amazon.com/blogs/big-data/building-multi-az-or-multi-region-amazon-redshift-clusters/但是，我不清楚如何您是否复制 Looker 的 PDT 表以支持通过 Route 53 到备用集群的即时故障转移？
Just curious about what people do to address the HA issue on Redshift?只是想知道人们如何解决 Redshift 上的 HA 问题？
2 个解决方案
解决方案1
0 2022-05-02 19:50:52
from the Q&A regarding high availability in case an AZ disruption scenario: "If your Amazon Redshift data warehouse cluster's Availability Zone becomes unavailable, Amazon Redshift will automatically move your cluster to another AWS Availability Zone (AZ) without any data loss or application changes. To activate this, you must enable the relocation capability in your cluster configuration settings."来自关于 AZ 中断情况下高可用性的问答：“如果您的 Amazon Redshift 数据仓库集群的可用区不可用，Amazon Redshift 将自动将您的集群移动到另一个 AWS 可用区 (AZ)，而不会丢失任何数据或更改应用程序。到激活它，您必须在集群配置设置中启用重定位功能。” https://aws.amazon.com/redshift/faqs/?nc1=h_ls https://aws.amazon.com/redshift/faqs/?nc1=h_ls
解决方案2
0 2022-11-30 17:43:30
Redshift now supports multi-AZ deployments: https://aws.amazon.com/redshift/reliability Redshift 现在支持多可用区部署： https://aws.amazon.com/redshift/reliability
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.