Menu
I've been waiting several hours for my redshift cluster complete a resize. It has been stuck at 99% complete with 0 time and 0 data remaining for 2 hours now. A quick web and forum search shows that this is fairly common. All the threads have no details about resolution, other than that an AWS rep PMs the user.
This is a cross-post from the AWS discussion forums.
761
Amazon Redshift clusters are elastic, cloud-based data warehouses that can be scaled both horizontally and vertically.
Amazon Redshift doesn't support tables with column-level privileges for cross-database queries. Amazon Redshift doesn't support concurrency scaling for the queries that read data from other databases. Amazon Redshift doesn't support query catalog objects on AWS Glue or federated databases.
An elastic resize allows you to add or remove nodes from the cluster by preserving the original configuration's slice count. However, it can introduce performance variation. If you want your node slices to match the number of slices in your target node type, use a classic resize.
I contacted AWS support in person (at the SF Market street loft).
It turns out that copying the last 1% of the data in a resize can take 80 to 90% of the time. In this case, the first 99% of the data was copied in 1 hour. The rest of the resize took 10 more hours. Unfortunately, neither the documentation nor the progress bar and time remaining indicators reflect this.
Your milage may vary.
140
I am sorry about your experience with the resize.
We are aware of the issue with display showing 99% for long time and we are working on providing our customers with better messaging about the resize progress.
Also I would love to see why did it take 2 hours to complete your resize process. Do you mind contacting me at [email protected] with more data so we can troubleshoot the issue?
33
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
