title: Achieving High Availability for Redshift?
body: <p>It is my understanding that Redshift is built for performance but not for Availability. 
  The documentation <a href="https://aws.amazon.com/redshift/faqs/" rel="nofollow noreferrer">https://aws.amazon.com/redshift/faqs/</a>
  suggest that once any node is down, the whole cluster is down until the node is restored. In the case of the AZ failure, you have no luck at all. </p>
  
  <p>This post suggests having a double cluster 
  <a href="https://aws.amazon.com/blogs/big-data/building-multi-az-or-multi-region-amazon-redshift-clusters/" rel="nofollow noreferrer">https://aws.amazon.com/blogs/big-data/building-multi-az-or-multi-region-amazon-redshift-clusters/</a>
  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?</p>
  
  <p>Just curious about what people do to address the HA issue on Redshift?</p>