Resizing Nodes for a Cluster

OCI Cache supports changing the number of nodes for an existing cluster if you need to scale up or down to meet your requirements.

When resizing nodes for a non-sharded cluster, you're configuring the number of nodes per cluster. OCI Cache supports a maximum of five nodes per non-sharded cluster. One node is configured as the primary, any more nodes are configured as replicas. If you increase the number of nodes for the cluster, you improve redundancy. For example, a three-node cluster gives you dual redundancy, with two replicas.

For reliability purposes, we recommend a minimum three node cluster configuration. Reliability isn't guaranteed for one to two node cluster configurations.

Increasing the cluster node count to greater than three improves readability.

When resizing nodes for a sharded cluster, you're configuring the number of nodes per shard. OCI Cache supports a maximum of five nodes per shard, with 100 nodes as the maximum number of nodes per cluster. For example, the following are valid cluster configurations:

  • 99 shards, with 1 node per shard.

  • 25 shards, with 4 nodes per shard.

  • 33 shards, with 3 nodes per shard.

These aren't the only possible cluster configurations, nor are they necessarily recommended cluster configurations, they're examples intended to illustrate valid node configurations for sharded clusters. You need to consider application requirements when deciding on the best configuration for clusters. For more information, see Configuring Sharded Clusters.

Note

You can only resize one configuration setting at a time, and you need to wait for a resize operation to complete before you can start a new resize operation.