Offline resharding and shard rebalancing for Redis (cluster mode enabled) - Amazon ElastiCache for Redis
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).

Offline resharding and shard rebalancing for Redis (cluster mode enabled)

The main advantage you get from offline shard reconfiguration is that you can do more than merely add or remove shards from your replication group. When you reshard offline, in addition to changing the number of shards in your replication group, you can do the following:

Note

Offline resharding is not supported on Redis clusters with data tiering enabled. For more information, see Data tiering.

  • Change the node type of your replication group.

  • Specify the Availability Zone for each node in the replication group.

  • Upgrade to a newer engine version.

  • Specify the number of replica nodes in each shard independently.

  • Specify the keyspace for each shard.

The main disadvantage of offline shard reconfiguration is that your cluster is offline beginning with the restore portion of the process and continuing until you update the endpoints in your application. The length of time that your cluster is offline varies with the amount of data in your cluster.

To reconfigure your shards Redis (cluster mode enabled) cluster offline

  1. Create a manual backup of your existing Redis cluster. For more information, see Taking manual backups.

  2. Create a new cluster by restoring from the backup. For more information, see Restoring from a backup into a new cache.

  3. Update the endpoints in your application to the new cluster's endpoints. For more information, see Finding connection endpoints.