search

awsdocs / amazon-elasticache-docs

The open source version of the Amazon ElastiCache User Guide. You can submit feedback and requests for changes by submitting issues in this repo or by making proposed changes and submitting a pull request.
Other
26 stars 78 forks source link

Outdated statement about resharding with cluster mode enabled #7

Closed hwatts closed 1 year ago

hwatts commented 5 years ago

In redis/CacheNodes.NodeGroups.md, there's the following statement, which caused us some confusion:

When you create a Redis (cluster mode enabled) cluster, you specify from 1 to 15 shards. Currently, however, unlike Redis (cluster mode disabled) clusters, once a Redis (cluster mode enabled) cluster is created, its structure cannot be altered in any way; you cannot add or delete nodes or shards. If you need to add or delete nodes, or change node types, you must create the cluster anew.

Is this still correct since it seems online resharding is now supported for Redis clusters, or am I misunderstanding the context here?

krishna81m commented 5 years ago

Cluster Mode Enabled - has conflicting documentation in the User Guide. https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/redis-ug.pdf

After a Redis (cluster mode enabled) cluster is created, its structure can't be altered in any way. You can't add or delete nodes or shards. If you need to add or delete nodes, or change node types, you must create the cluster again. ...

Replace any node in a Redis (cluster mode enabled) shard – To replace the node in a cluster with no downtime, use online resharding. First add a shard by scaling out, and then delete the shard with the node to be replaced by scaling in. To replace any node in a Redis (cluster mode enabled) cluster

  1. Scale out: Add an additional shard with the same configuration as the existing shard with the node to be replaced. For more information, see Adding Shards with Online Resharding (p. 252).
joshbean commented 1 year ago

Closing this issue or pull request in advance of archiving this repo. For more information about the decision to archive this repo (and others in the 'awsdocs' org), see the announcement on the AWS News Blog.