ApsaraDB for Redis master-replica instances provide not only high-performance caching service, but also high data reliability.
A master-replica instance runs in a master-replica structure. The master provides services for your business, and the replica works to ensure high availability (HA). When the master fails, the system switches services to the replica within 30 seconds to ensure stability of services.
In the master-replica architecture, the master the and replica run on different physical servers. The master provides services for your business. You can use Redis command-line interface (CLI) commands and common clients to add, modify, search, and delete data in a database. When the master fails, the proprietary HA system performs the failover operation to ensure stability of services.
- Reliable data
By default, the master-replica instance enables data persistence to write all data to disks. The system supports data replication. You can roll back or clone instances based on RDB files, and effectively solve issues caused by accidental operations. The system also supports zone-disaster recovery.
The master-replica instance is developed on the basis of open-source Redis and 100% compatible with Redis commands. You can smoothly migrate an on-premises Redis database to an ApsaraDB for Redis master-replica instance. You can also use Data Transmission Service (DTS) to smoothly migrate incremental Redis data.
- Proprietary features
ApsaraDB for Redis encapsulates the HA system to detect failures on the master in real time. In this way, the system can effectively solve issues such as disk I/O errors and CPU failures and perform the failover operation in time to ensure high availability of services.
- Master-replica replication mechanism
Alibaba Cloud has customized the master-replica replication mechanism in ApsaraDB for Redis. You can replicate data in the format of incremental logs between the master and the replica . When the replication is interrupted, system performance and stability is unchanged and free from issues caused by the master-replica replication mechanism of the original Redis database.
Some issues caused by the master-replica replication mechanism of the original Redis database are described as follows:
- When the replication is interrupted, the replica runs the Partial Resynchronization (PSYNC) command to resynchronize partial data. During this process, the resynchronization fails. The master has to fully synchronize RDB files to the replica.
- To fully synchronize RDB files, the master has to perform full replication first due to the single-thread model. As a result, the master lags for several milliseconds or seconds.
- The single-thread process leads to the use of the copy-on-write (CoW or COW) mechanism. The mechanism utilizes memory on the master. This may run out of memory and cause the application to exit abnormally.
- The replica files that the master generates utilize disk I/O and CPU resources.
- The replication of GB-level files may lead to outgoing traffic bursts on the server and increase the sequential I/O throughput of disks. This affects normal response of services and cause more issues.
- Compatibility with Redis protocols
The master-replica instance is fully compatible with Redis protocols, so you can smoothly migrate your business.
- Persistent data storage based on ApsaraDB for Redis
The master-replica instance supports data persistence, replication and recovery to ensure data reliability.
- Limited QPS performance
The original Redis database runs in a single-thread mechanism. In scenarios where QPS is 100,000 or less, we recommend that you use this edition. If you require higher performance, select a cluster instance.
- Redis commands are simple and contain few sorting and compute commands
CPU may be bottlenecked due to Redis single-thread mechanism. If you require plenty of sorting and compute operations, we recommend that you select a cluster instance.