Scale a Redis cluster
Scale a Redis cluster
Redis cloud database cluster can be scale. For example:
- Increase RAM to improve cluster performance;
- change a fixed node configuration to another fixed configuration — disk and RAM size must necessarily be larger than in the previous configuration, the number of vCPUs can be reduced or increased.
Check out the list node configurations.
Configuration change process depends on the availability of replicas.
Principle of operation
The process of changing the configuration depends on the availability of replicas:
- if there are no replicas in the cluster — the master node will be stopped while the changes are applied, the cluster will be temporarily unavailable for reading and writing;
- if there are replicas in the cluster — the cluster will be read and write accessible while the changes are being applied. The replicas will be stopped one by one and the configuration of each replica will be changed. The master node will then switch to one of the replicas and the configuration of the past master node will be changed.
The configuration change time depends on the amount of data in the cluster.
Scale up the cluster
- Scale the cluster when users are least active.
- To avoid stopping a master node in a cluster with no replicas, we first add a line. After scaling, the replica can be deleted.
- In control panel go to Cloud platform → Databases.
- Open the cluster page → tab Settings.
- Click Scale up the cluster.
- Pick another fixed configuration. You can only select a configuration with more RAM and disk space. The number of vCPUs can be reduced or increased.
- Optional: increase the number of lines in the cluster.
- Click Save.
- After scaling clear the DNS cache.
- Verify that the cluster has scaled correctly.
Clear DNS cache
Ubuntu/Debian
CentOS
macOS
Windows
-
Open the CLI.
-
Clear the DNS cache:
sudo systemctl restart systemd-resolved
-
Open the CLI.
-
Clear the DNS cache:
sudo dscacheutil -flushcache
-
Open the CLI.
-
Clear the DNS cache:
sudo systemctl restart network
-
Open the CLI with administrator privileges.
-
Clear the DNS cache:
ipconfig /flushdns