3 Respostas
- Mais recentes
- Mais votos
- Mais comentários
2
FYI, I opened up a trouble ticket and they told me that I will need to delete the cluster and create a new one from backup. If you use the same cluster name, the endpoint will also be the same. It will have a different IP, but the conx string should be the same.
edit: My redshift instance finally came back online!
respondido há 2 anos
1
Same problem here. Ours is stuck in Modifying too since the outage yesterday.
respondido há 2 anos
0
Same problem here. Production database has started modification without any prerequisites. Because of that modification, production Redshift cluster is unreachable anymore.
respondido há um ano
Conteúdo relevante
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 3 anos
- AWS OFICIALAtualizada há 2 anos
How did you solve this? I'm facing the same problem with Redshift serverless. I could not query data and delete the namespace/workgroup.