By using AWS re:Post, you agree to the Terms of Use

Node type missing in wizard when attempting to scale redis node

0

We have a redis node configured in the following way:

Mode: Redis
Engine: 5.0.4
Shards: 0
Nodes: 1
Node Type: cache.t2.medium
Status: available
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.

asked 3 years ago26 views
3 Answers
0

Hi,
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.

Link: https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/CacheNodes.NodeReplacement.html#ReplaceStandalone

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.
Link: https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/backups-restoring.html#backups-restoring-CON

Hope this helps!
-randy

answered 3 years ago
0

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 .

answered 3 years ago
0

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

answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions