3 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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!
répondu il y a 2 ans
1
Same problem here. Ours is stuck in Modifying too since the outage yesterday.
répondu il y a 2 ans
0
Same problem here. Production database has started modification without any prerequisites. Because of that modification, production Redshift cluster is unreachable anymore.
répondu il y a un an
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a 2 ans
How did you solve this? I'm facing the same problem with Redshift serverless. I could not query data and delete the namespace/workgroup.