redshift resume issue today

0

Do we have an issue on the redshift resume function today? I resumed a 1 node dc2.large for testing and its been almost an hour in modifying (resume) state. Normally it resumes after 5 to 10 minutes. Thanks

cgm
질문됨 2년 전542회 조회
1개 답변
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.
AWS
답변함 2년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠