3개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
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!
답변함 2년 전
0
Same problem here. Production database has started modification without any prerequisites. Because of that modification, production Redshift cluster is unreachable anymore.
답변함 일 년 전
관련 콘텐츠
- AWS 공식업데이트됨 3년 전
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 2년 전
How did you solve this? I'm facing the same problem with Redshift serverless. I could not query data and delete the namespace/workgroup.