1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
I assume that you checked the cluster status on the Redshift console. In that case, it's possible that your cluster was already available but the Redshift console didn't update it until an hour later.
My workaround: use AWS CLI to check the cluster status every couple of minutes. For example, run this command:
aws redshift describe-clusters --cluster-identifier 'cluster_identifier/name' --query 'Clusters[].{ClusterIdentifier:ClusterIdentifier,ClusterStatus:ClusterStatus,ClusterAvailabilityStatus:ClusterAvailabilityStatus}' --region XXX --profile YYY
and you'll see something like
[
{
"ClusterIdentifier": "cluster-name",
"ClusterStatus": "available",
"ClusterAvailabilityStatus": "Available"
}
]
This cluster status result from AWS CLI is apparently more reliable than the Redshift console.
- If the status shows "resuming" for a long time: it means the resume process indeed takes longer and you should reach out to the AWS Premium Support.
- If the status shows "available" shortly in 5~10min: your cluster is available now, try connecting to it with SQL client apps. When Redshift console shows the cluster is resuming, you can't use the Redshift Query Editor.
- Otherwise if the below workaround doesn't work for you, or you are seeking for a permanent fix, open a case to the AWS Premium Support, Redshift team.
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 5 mesi fa
- AWS UFFICIALEAggiornata 3 anni fa