Manually scaling for Memcached - Amazon ElastiCache
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Manually scaling for Memcached

Manually horizontally scaling a Memcached cluster in or out is as easy as adding or removing nodes from the cluster. Memcached clusters are composed of 1 to 60 nodes.

Because you can partition your data across all the nodes in a Memcached cluster, scaling up to a node type with greater memory is seldom required. However, because the Memcached engine does not persist data, if you do scale to a different node type then your new cluster starts out empty unless your application populates it.

To manually vertically scale your Memcached cluster, you must create a new cluster. Memcached clusters always start out empty unless your application populates it.

Manually scaling Memcached Clusters
Action Topic

Scaling out

Adding nodes to a cluster

Scaling in

Deleting nodes from a cluster

Changing node types

Manually scaling Memcached vertically

Manually scaling Memcached horizontally

The Memcached engine supports partitioning your data across multiple nodes. Because of this, Memcached clusters scale horizontally easily. To horizontally scale your Memcached cluster, merely add or remove nodes.

The following topics detail how to scale your Memcached cluster out or in by adding or removing nodes.

Each time you change the number of nodes in your Memcached cluster, you must re-map at least some of your keyspace so it maps to the correct node. For more detailed information on load balancing your Memcached cluster, see Configuring your ElastiCache client for efficient load balancing (Memcached).

If you use auto discovery on your Memcached cluster, you do not need to change the endpoints in your application as you add or remove nodes. For more information on auto discovery, see Automatically identify nodes in your cluster (Memcached) If you do not use auto discovery, each time you change the number of nodes in your Memcached cluster you must update the endpoints in your application.

Manually scaling Memcached vertically

When you manually scale your Memcached cluster up or down, you must create a new cluster. Memcached clusters always start out empty unless your application populates it.

Important

If you are scaling down to a smaller node type, be sure that the smaller node type is adequate for your data and overhead. For more information, see Choosing your node size.

Scaling Memcached vertically (Console)

The following procedure walks you through scaling your cluster vertically using the ElastiCache console.

To scale a Memcached cluster vertically (console)
  1. Create a new cluster with the new node type. For more information, see Creating a Memcached cluster (console).

  2. In your application, update the endpoints to the new cluster's endpoints. For more information, see Finding a Cluster's Endpoints (Console) (Memcached).

  3. Delete the old cluster. For more information, see Deleting a new node in Memcached.

Scaling Memcached vertically (Amazon CLI)

The following procedure walks you through scaling your Memcached cache cluster vertically using the Amazon CLI.

To scale a Memcached cache cluster vertically (Amazon CLI)
  1. Create a new cache cluster with the new node type. For more information, see Creating a cluster (Amazon CLI).

  2. In your application, update the endpoints to the new cluster's endpoints. For more information, see Finding Endpoints (Amazon CLI).

  3. Delete the old cache cluster. For more information, see Using the Amazon CLI to delete an ElastiCache cluster.

Scaling Memcached vertically (ElastiCache API)

The following procedure walks you through scaling your Memcached cache cluster vertically using the ElastiCache API.

To scale a Memcached cache cluster vertically (ElastiCache API)
  1. Create a new cache cluster with the new node type. For more information, see Creating a cluster for Memcached (ElastiCache API)

  2. In your application, update the endpoints to the new cache cluster's endpoints. For more information, see Finding Endpoints (ElastiCache API).

  3. Delete the old cache cluster. For more information, see Using the ElastiCache API.