- Newest
- Most votes
- Most comments
When migrating from DC2 to RA3 nodes in Amazon Redshift, there are several potential reasons why your resize operations might be failing silently:
-
Availability Zone Compatibility: While you mentioned us-east-1e, there's no known specific AZ issue with DC2 to RA3 migrations. However, RA3 nodes might have different availability requirements than DC2 nodes.
-
Cluster Configuration: For a 2-node DC2 cluster, the recommended migration path to RA3 is typically 1:1 for DC2.large to RA3.large (1 node of RA3.large for every 1 node of DC2.large). Your approach of going from 2-node DC2.large to 2-node RA3.large aligns with the recommended sizing guidance.
-
Single-Node vs. Multi-Node Considerations: If you were trying to go from a multi-node to a single-node configuration, this would require a classic resize rather than elastic resize, but you're maintaining the same node count, so this shouldn't be the issue.
-
Alternative Migration Options: Since both classic resize and scheduled resize are failing, you might need to consider the snapshot restore method. This involves:
- Creating a snapshot of your existing cluster
- Restoring to a new cluster with RA3 nodes
- Updating your endpoint references
Note that with the snapshot restore method, your cluster endpoint will change, and any data written to the source cluster after the snapshot is taken would need to be manually copied over.
-
RA3 Upgrade Credits: Regarding your concern about qualifying for RA3 upgrade credits, I would recommend contacting AWS Support directly to confirm if the snapshot restore method would still qualify for the upgrade credits being offered for DC2 to RA3 migrations.
-
Reserved Nodes Consideration: If you have reserved nodes for your DC2 cluster, note that reserved nodes are only available for RA3 types now, so you would need to complete the migration to RA3 before purchasing reserved nodes.
Since you've already tried multiple approaches without success, opening a support case with AWS might be the most efficient path forward to identify the specific cause of the silent failures and determine the best migration strategy for your situation.
Sources
Amazon Redshift DC2 to RA3 Migration best practices | AWS re:Post
Classic Resize Redshift Cluster status on modifying | AWS re:Post
CancelResize - Amazon Redshift
Changing cluster from dc2.large 4 nodes to ra3.xlplus 1 node | AWS re:Post
Reserved nodes in Redshift having On-demand cluster | AWS re:Post
Relevant content
asked a year ago
asked 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 8 months ago
