3 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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!
con risposta 2 anni fa
1
Same problem here. Ours is stuck in Modifying too since the outage yesterday.
con risposta 2 anni fa
0
Same problem here. Production database has started modification without any prerequisites. Because of that modification, production Redshift cluster is unreachable anymore.
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata un anno fa
How did you solve this? I'm facing the same problem with Redshift serverless. I could not query data and delete the namespace/workgroup.