Using the Amazon Web Services Management Console Scaling down Redis OSS cache clusters (Amazon CLI)Scaling down Redis OSS cache clusters (ElastiCache API)

Online scaling down

Topics

Scaling down Redis OSS cache clusters (Console)
Scaling down Redis OSS cache clusters (Amazon CLI)
Scaling down Redis OSS cache clusters (ElastiCache API)

Scaling down Redis OSS cache clusters (Console)

The following procedure describes how to scale down a Redis OSS cluster using the ElastiCache Management Console. During this process, your Redis OSS cluster will continue to serve requests with minimal downtime.

To scale Down a Redis OSS cluster (console)

Sign in to the Amazon Web Services Management Console and open the ElastiCache console at https://console.amazonaws.cn/elasticache/.
From the navigation pane, choose Redis OSS clusters.
From the list of clusters, choose your preferred cluster.
Choose Modify.
In the Modify Cluster wizard:
1. Choose the node type you want to scale to from the Node type list. To scale down, select a node type smaller than your existing node. Note that not all node types are available to scale down to.
If you want to perform the scale down process right away, choose the Apply immediately box. If the Apply immediately box is not chosen, the scale-down process is performed during this cluster's next maintenance window.
Choose Modify.

If you chose Apply immediately in the previous step, the cluster's status changes to modifying. When the status changes to available, the modification is complete and you can begin using the new cluster.

Scaling down Redis OSS cache clusters (Amazon CLI)

The following procedure describes how to scale down a Redis OSS cache cluster using the Amazon CLI. During this process, your Redis OSS cluster will continue to serve requests with minimal downtime.

To scale down a Redis OSS cache cluster (Amazon CLI)

Determine the node types you can scale down to by running the Amazon CLI list-allowed-node-type-modifications command with the following parameter.

For Linux, OS X, or Unix:


aws elasticache list-allowed-node-type-modifications \
	    --replication-group-id my-replication-group-id

For Windows:


aws elasticache list-allowed-node-type-modifications ^
	    --replication-group-id my-replication-group-id

Output from the above command looks something like this (JSON format).


{
	    "ScaleUpModifications": [
	        "cache.m3.2xlarge", 
	        "cache.m3.large", 
	        "cache.m3.xlarge", 
	        "cache.m4.10xlarge", 
	        "cache.m4.2xlarge", 
	        "cache.m4.4xlarge", 
	        "cache.m4.large", 
	        "cache.m4.xlarge", 
	        "cache.r3.2xlarge", 
	        "cache.r3.4xlarge", 
	        "cache.r3.8xlarge", 
	        "cache.r3.large", 
	        "cache.r3.xlarge"
	    ]
	
	       "ScaleDownModifications": [
	        "cache.t2.micro", 
	        "cache.t2.small ", 
	        "cache.t2.medium ",
  	      "cache.t1.small"
	    ]
}

For more information, see list-allowed-node-type-modifications in the Amazon CLI Reference.

Modify your replication group to scale down to the new, smaller node type, using the Amazon CLI modify-replication-group command and the following parameters.

--replication-group-id – The name of the replication group you are scaling down to.
--cache-node-type – The new node type you want to scale the cache cluster. This value must be one of the node types returned by the list-allowed-node-type-modifications command in step 1.
--cache-parameter-group-name – [Optional] Use this parameter if you are using reserved-memory to manage your cluster's reserved memory. Specify a custom cache parameter group that reserves the correct amount of memory for your new node type. If you are using reserved-memory-percent you can omit this parameter.
--apply-immediately – Causes the scale-up process to be applied immediately. To postpone the scale-down process to the cluster's next maintenance window, use the --no-apply-immediately parameter.

For Linux, OS X, or Unix:


aws elasticache modify-replication-group  \
	    --replication-group-id my-redis-cluster \
	    --cache-node-type cache.t2.micro \	    
	    --apply-immediately

For Windows:


aws elasticache modify-replication-group ^
	    --replication-group-id my-redis-cluster ^
	    --cache-node-type cache.t2.micro ^	   
	    --apply-immediately

Output from the above command looks something like this (JSON format).



{	
		"ReplicationGroup": {
        "Status": "modifying",
        "Description": "my-redis-cluster",
        "NodeGroups": [
            {
                "Status": "modifying",
                "Slots": "0-16383",
                "NodeGroupId": "0001",
                "NodeGroupMembers": [
                    {
                        "PreferredAvailabilityZone": "us-east-1f",
                        "CacheNodeId": "0001",
                        "CacheClusterId": "my-redis-cluster-0001-001"
                    },
                    {
                        "PreferredAvailabilityZone": "us-east-1d",
                        "CacheNodeId": "0001",
                        "CacheClusterId": "my-redis-cluster-0001-002"
                    }
                ]
            }
        ],
        "ConfigurationEndpoint": {
            "Port": 6379,
            "Address": "my-redis-cluster.r7gdfi.clustercfg.use1.cache.amazonaws.com"
        },
        "ClusterEnabled": true,
        "ReplicationGroupId": "my-redis-cluster",
        "SnapshotRetentionLimit": 1,
        "AutomaticFailover": "enabled",
        "SnapshotWindow": "07:30-08:30",
        "MemberClusters": [
            "my-redis-cluster-0001-001",
            "my-redis-cluster-0001-002"
        ],
        "CacheNodeType": "cache.t2.micro",
         "DataTiering": "disabled"
        "PendingModifiedValues": {}
    }
}

For more information, see modify-replication-group in the Amazon CLI Reference.

If you used the --apply-immediately, check the status of the cache cluster using the Amazon CLI describe-cache-clusters command with the following parameter. When the status changes to available, you can begin using the new, smaller cache cluster node.

Scaling down Redis OSS cache clusters (ElastiCache API)

The following process scales your replication group from its current node type to a new, smaller node type using the ElastiCache API. During this process, your Redis OSS cluster will continue to serve requests with minimal downtime.

The amount of time it takes to scale down to a smaller node type varies, depending upon your node type and the amount of data in your current cache cluster.

Scaling down (ElastiCache API)

Determine which node types you can scale down to using the ElastiCache API ListAllowedNodeTypeModifications action with the following parameter.
- ReplicationGroupId – the name of the replication group. Use this parameter to describe a specific replication group rather than all replication groups.
```
https://elasticache.us-west-2.amazonaws.com/
	   ?Action=ListAllowedNodeTypeModifications
	   &ReplicationGroupId=MyReplGroup
	   &Version=2015-02-02
	   &SignatureVersion=4
	   &SignatureMethod=HmacSHA256
	   &Timestamp=20150202T192317Z
	   &X-Amz-Credential=<credential>
```
For more information, see ListAllowedNodeTypeModifications in the Amazon ElastiCache API Reference.
Scale your current replication group down to the new node type using the ModifyReplicationGroup ElastiCache API action and with the following parameters.
- ReplicationGroupId – the name of the replication group.
- CacheNodeType – the new, smaller node type of the cache clusters in this replication group. This value must be one of the instance types returned by the ListAllowedNodeTypeModifications action in the previous step.
- CacheParameterGroupName – [Optional] Use this parameter if you are using reserved-memory to manage your cluster's reserved memory. Specify a custom cache parameter group that reserves the correct amount of memory for your new node type. If you are using reserved-memory-percent you can omit this parameter.
- ApplyImmediately – Set to true to causes the scale-down process to be applied immediately. To postpone the scale-down process to the next maintenance window, use ApplyImmediately=false.
```
https://elasticache.us-west-2.amazonaws.com/
	   ?Action=ModifyReplicationGroup
	   &ApplyImmediately=true
	   &CacheNodeType=cache.t2.micro
	   &CacheParameterGroupName=redis32-m3-2xl
	   &ReplicationGroupId=myReplGroup
	   &SignatureVersion=4
	   &SignatureMethod=HmacSHA256
	   &Timestamp=20141201T220302Z
	   &Version=2014-12-01
	   &X-Amz-Algorithm=&AWS;4-HMAC-SHA256
	   &X-Amz-Date=20141201T220302Z
	   &X-Amz-SignedHeaders=Host
	   &X-Amz-Expires=20141201T220302Z
	   &X-Amz-Credential=<credential>
	   &X-Amz-Signature=<signature>
```
For more information, see ModifyReplicationGroup in the Amazon ElastiCache API Reference.

Javascript is disabled or is unavailable in your browser.

To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.

Online scaling up

Getting started with JSON in ElastiCache (Redis OSS)