Node type missing in wizard when attempting to scale redis node
We have a redis node configured in the following way:
Node Type: cache.t2.medium
Update Action Status: up to date
It appears that we cannot change the node type from the modify cluster wizard. The "Node type" option is not present in the wizard at all.
How would we go about scaling up? Would we need to do the following?
- Backup the cache.
- Create a new node with the appropriate instance type.
- Restore the backup in the new node.
Delete the original node.
Any guidance is much appreciated.
Yes, if you only want to scale up with a single node, you can following the AWS guide to Replace the only node in any Redis cluster
To replace the only node using backup and restore 1. Create a snapshot of the node's cluster. For instructions, see Making Manual Backups. 2. Create a new cluster seeding it from the snapshot. For instructions, see Restoring From a Backup with Optional Cluster Resizing. 3. Delete the cluster with the node scheduled for replacement. For instructions, see Deleting a Cluster. 4. In your application, replace the old node's endpoint with the new node's endpoint.
When you perform Step 2 (Restoring from a Backup using Console), you are presented with the Node Type option to specify the larger node type.
Hope this helps!
Thanks Randy for confirming what I suspected. I will proceed as described in the article https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/CacheNodes.NodeReplacement.html#ReplaceStandalone .
Actually, one further question. Is there a way of avoiding the need to replace the old node's endpoint with the new node's endpoint in our applications? Can we keep the old one and map it to the new Redis node?
Edited by: ec-confounder on Aug 19, 2019 2:54 AM
Node type missing in wizard when attempting to scale redis nodeasked 3 years ago
Adding new shards didn't increase the total available memoryasked 2 years ago
Elasticache Single node - Read endpointAccepted Answerasked a year ago
Unable to connect to redis cluster with node client, what am I doing wrong?asked 5 months ago
Connecting to elastiCache cluster with node.jsasked a month ago
Elasticache for Redis cluster service update got stuckasked 3 months ago
Redis cluster with multiple shardsasked 3 years ago
ElastiCache multi-AZ setup with no replicaAccepted AnswerEXPERTasked 2 years ago
Problem upgrading AWS ElastiCache Redis clusterasked 3 months ago
ElastiCache for Redis load distributionasked 4 months ago