Describes database replication and high availability as it affects Redis Cloud.
| Redis Cloud |
|---|
Database replication helps ensure high availability.
When replication is enabled, your dataset is duplicated to create a replica that is synchronized with the primary dataset.
Replication allows for automatic failover and greater fault tolerance. It can prevent data loss in the event of a hardware or zone failure.
Redis Cloud supports three levels of replication:
No replication means that you will have a single copy of your database.
Single-zone replication means that your database will have a primary and a replica located in the same cloud zone. If anything happens to the primary, the replica takes over and becomes the new primary.
Multi-zone replication means that the primary and its replicas are stored in different zones. This means that your database can remain online even if an entire zone becomes unavailable.
Your replication options depend on your subscription plan:
Whether or not you can change your replication settings after database creation depends on your plan type and what type of replication you originally selected.
Replication can affect performance as traffic increases to synchronize all copies.
For both Redis Cloud Essentials and Redis Cloud Pro, replication requires a memory limit that is double the dataset size of your database.
For Redis Cloud Essentials, the size of the plan you choose includes replication. Therefore, if you choose replication, the dataset size you can use is half of the stated plan size. For example, if you choose a 1 GB plan, Redis allocates 512 MB for the dataset size, and the other 512 MB for replication.
For Redis Cloud Pro, you select your dataset size when you create your database, and we calculate your memory limit based on the replication settings you choose.
Zone settings can only be defined when a subscription is created. You cannot change these settings once the subscription becomes active.
This means you can't convert a multi-zone subscription to a single zone (or vice-versa).
To use different zone settings, create a new subscription with the preferred settings and then migrate data from the original subscription.
You can reduce network transfer costs and network latency by ensuring your Redis Cloud Pro cluster and your application are located in the same availability zone.
To specify the availability zone(s) for your cluster, create your Pro database with custom settings, and select Manual Selection under Allowed Availability Zones in Advanced options.
For Google Cloud clusters and Redis Cloud BYOC, select an availability zone from the Zone name list.
Select one availability zone when Multi-AZ is turned off.For all other AWS clusters, select an availability zone ID from the Zone IDs list. For more information on how to find an availability zone ID, see the AWS docs.
For hosted AWS clusters, select availability zone IDs from the Zone IDs list.If Multi-AZ is enabled, you must select three availability zones from the list.
Select Manual selection to select three availability zones when Multi-AZ is enabled.For more information on availability zones, see the Google Cloud docs or the AWS docs.
To learn more about high availability and replication, see:
