Redshift Test Driver [dc2 - ra3]

Question

Hello, I would like to test new RA3 nodes as older ones (DC2) are deprecated. I tried to use instructions I got via email, but on StepFunction starting got an error

```
{
  "errorMessage": "An error occurred (InvalidParameterCombination) when calling the RestoreFromClusterSnapshot operation: The node type ra3.4xlarge is not currently available on track DC2LTM.",
  "errorType": "ClientError",
  "stackTrace": [
    "  File "/var/task/RedshiftConfigTestingLambda.py", line 138, in handler
    "status": create_cluster(
",
    "  File "/var/task/RedshiftConfigTestingLambda.py", line 1001, in create_cluster
    client.restore_from_cluster_snapshot(
",
    "  File "/opt/python/lib/python3.8/site-packages/botocore/client.py", line 514, in _api_call
    return self._make_api_call(operation_name, kwargs)
",
    "  File "/opt/python/lib/python3.8/site-packages/botocore/client.py", line 938, in _make_api_call
    raise error_class(parsed_response, operation_name)
"
  ]
}
```
So it seems it's not possible to test workload on RA3 nodes, using a snapshot of my current cluster (DC2 nodes). Am I right? If "yes" - how can I verify that new nodes will be able to handle our workload?

re:Post Agent · Answer

You're encountering an issue because your DC2 cluster is on the DC2LTM (Long Term Maintenance) track, which is preventing direct testing with RA3 nodes using the Test Drive utility.

This is expected behavior as DC2 node type development will stop at Redshift release P191, and all DC2 clusters will be migrated to the LTM track. On this track, clusters will receive only critical updates until their retirement on April 23rd, 2026, but customers won't be able to change tracks.

To verify that RA3 nodes can handle your workload, you have a few options:

1. Use the snapshot restore method to create a new RA3 cluster:
- Create a snapshot of your existing DC2 cluster
- Restore this snapshot to a new cluster with RA3 nodes
- Test your workload on this new cluster

2. For Redshift Serverless testing:
- Create a snapshot from your DC2 cluster
- Restore the snapshot to a Redshift Serverless namespace
- Test your workload performance

The Amazon Redshift Test Drive utility should work if you first create a new cluster with RA3 nodes using a snapshot of your DC2 cluster, and then use that cluster for testing.

When sizing your test environment, follow these guidelines:
- For DC2.large nodes: 1 node of RA3.large for every 1 node of DC2.large
- For DC2.8xlarge nodes: 2 nodes of RA3.4xlarge for every 1 node of DC2.8xlarge (if you have 2-15 nodes)

After migration, monitor your query performance and adjust the node count as needed to meet your performance requirements.  
**Sources**  
[Amazon Redshift DC2 to RA3 Migration best practices | AWS re:Post](https://repost.aws/articles/ARqonrT0T6R9-McFa4C10Uog/amazon-redshift-dc2-to-ra3-migration-best-practices)  
[DC2 to RA3 migration, resize failing silently after multiple attempts | AWS re:Post](https://repost.aws/questions/QUzJRS8dW_QNuu0Vu7eLMnHA/dc2-to-ra3-migration-resize-failing-silently-after-multiple-attempts)

Redshift Test Driver [dc2 -> ra3]

Add your answer

Relevant content