ApsaraDB for Redis is a database service compatible with the open source Redis protocol and provides hybrid storage of memory and disks. Based on reliable hot standby architectures and scalable cluster architectures, ApsaraDB for Redis is suitable for scenarios that require flexible configuration changes, high throughput, and low latency. This topic describes how to synchronize data from a Codis cluster to an ApsaraDB for Redis instance by using Data Transmission Service (DTS).
- The destination ApsaraDB for Redis instance is created, and the database version of the instance is 4.0, 5.0 or 6.0. For more information, see Step 1: Create an ApsaraDB for Redis instance.
- The available storage capacity of the destination ApsaraDB for Redis instance is larger than the total size of data stored in the source Codis cluster.
- All master nodes in the source Codis cluster support the
- The timeout period for data replication between the master and replica nodes in the source instance is specified by the repl-timeout parameter. By default, this parameter is set to 60 seconds. We recommend that you run the
config set repl-timeout 600command to set this parameter to 600 seconds. If the source instance stores a large amount of data, you can increase the value of the repl-timeout parameter based on your business requirements.
How DTS synchronizes data from a Codis cluster
A Codis cluster consists of multiple Codis-Groups. You must create a data synchronization task for each Codis-Group. DTS synchronizes each Codis-Group in a data synchronization task until the whole cluster is synchronized.
Architecture of the Codis cluster
In this topic, the Codis cluster consists of two Codis-Groups. Each Codis-Group runs in a master-replica architecture. The following figure shows the architecture of the cluster.
- DTS uses the resources of the source and destination instances during initial full data synchronization. This may increase the loads on the database servers. If you synchronize a large volume of data or if the server specifications cannot meet your requirements, database services may become unavailable. Before you synchronize data, evaluate the impact of data synchronization on the performance of the source and destination instances. We recommend that you synchronize data during off-peak hours.
- If the
bindparameter is configured in the redis.conf file of the source Redis database, you must set the value of this parameter to the internal IP address of the ECS instance. The setting ensures that DTS can connect to the source database.
- To ensure the stability of data synchronization, we recommend that you increase the value of the repl-backlog-size parameter in the
redis.conffile of the source Codis cluster.
- To ensure the synchronization quality, DTS adds the following key to the source Codis cluster:
DTS_REDIS_TIMESTAMP_HEARTBEAT. This key is used to record the time when data is synchronized to ApsaraDB for Redis.
- We recommend that you do not run the
FLUSHALLcommand in the source Codis cluster. Otherwise, data may become inconsistent between the source and destination databases.
- By default, the maxmemory-policy parameter that specifies how data is evicted is set to volatile-lru for ApsaraDB for Redis instances. If the destination instance has insufficient memory, data inconsistency may occur between the source and destination instances due to data eviction. In this case, the data synchronization task does not stop running.
To prevent data inconsistency, we recommend that you set maxmemory-policy to noeviction for the destination instance. This way, the data synchronization task fails if the destination instance has insufficient memory, but data loss can be prevented for the destination instance.Note For more information about data eviction policies, see How does ApsaraDB for Redis evict data by default?
- If an expiration policy is enabled for specific keys in the source database, these keys may not be deleted at the earliest opportunity after they expire. Therefore, the number of keys in the destination database may be less than that in the source database. You can run the INFO command to view the number of keys in the destination database. Note The number of keys that do not have the expiration policy enabled or have not expired is the same between the source and destination databases.
- The database version of the destination ApsaraDB for Redis instance can be 4.0, 5.0 or 6.0. The version of the destination database must be the same as or later than the version of the source database. If you synchronize data between different versions of Redis databases, make sure that the versions of the source and destination databases are compatible. For example, you can create a pay-as-you-go destination instance to check the compatibility between the source and destination instances. Then, you can release this instance or change the billing method of the instance to subscription.
- If the destination instance is deployed in a cluster architecture and the amount of memory used by a shard in the destination instance reaches the upper limit, or if the available storage space of the destination instance is insufficient, the data synchronization task fails due to out of memory (OOM).
- If the transparent data encryption (TDE) feature is enabled for the destination instance, you cannot use DTS to synchronize data.
|Synchronization type||Task configuration fee|
|Schema synchronization and full data synchronization||Free of charge.|
|Incremental data synchronization||Charged. For more information, see Billing overview.|
Supported synchronization topologies
- One-way one-to-one synchronization
- One-way one-to-many synchronization
- One-way cascade synchronization
For more information, see Synchronization topologies.
Commands that can be synchronized
- BITOP, BLPOP, BRPOP, and BRPOPLPUSH
- DECR, DECRBY, and DEL
- EVAL, EVALSHA, EXEC, EXPIRE, and EXPIREAT
- GEOADD and GETSET
- HDEL, HINCRBY, HINCRBYFLOAT, HMSET, HSET, and HSETNX
- INCR, INCRBY, and INCRBYFLOAT
- LINSERT, LPOP, LPUSH, LPUSHX, LREM, LSET, and LTRIM
- MOVE, MSET, MSETNX, and MULTI
- PERSIST, PEXPIRE, PEXPIREAT, PFADD, PFMERGE, PSETEX, and PUBLISH
- RENAME, RENAMENX, RESTORE, RPOP, RPOPLPUSH, RPUSH, and RPUSHX
- SADD, SDIFFSTORE, SELECT, SET, SETBIT, SETEX, SETNX, SETRANGE, SINTERSTORE, SMOVE, SPOP, SREM, and SUNIONSTORE
- ZADD, ZINCRBY, ZINTERSTORE, ZREM, ZREMRANGEBYLEX, ZUNIONSTORE, ZREMRANGEBYRANK, and ZREMRANGEBYSCORE
- PUBLISH operations cannot be synchronized.
- If you run the EVAL or EVALSHA command to call Lua scripts, DTS cannot identify whether these Lua scripts are executed on the destination instance. This is because the destination instance does not explicitly return the execution results of Lua scripts during incremental data synchronization.
- When DTS runs the SYNC or PSYNC command to transfer data of the LIST type, DTS does not clear the existing data in the destination instance. As a result, the destination instance may contain duplicate data records.
- Purchase a data synchronization instance. For more information, see Purchase a DTS instance. Note On the buy page, set the Source Instance parameter to Redis, the Destination Instance parameter to Redis, and the Synchronization Topology parameter to One-Way Synchronization.
- Log on to the DTS console. Note If you are redirected to the Data Management (DMS) console, you can click the icon in the lower-right corner to go to the previous version of the DTS console.
- In the left-side navigation pane, click Data Synchronization.
- In the upper part of the Data Synchronization Tasks page, select the region in which the destination instance resides.
- Find the data synchronization instance and click Configure Task in the Actions column.
- Configure the source and destination instances.
Section Parameter Description N/A Synchronization Task Name The task name that DTS automatically generates. We recommend that you specify a descriptive name that makes it easy to identify the task. You do not need to use a unique task name. Source Instance Details Instance Type The access method of the destination database. Select User-Created Database in ECS Instance. Instance Region The source region that you selected on the buy page. You cannot change the value of this parameter. ECS Instance ID The ID of the Elastic Compute Service (ECS) instance that hosts the master node of the codis-group.Note DTS synchronizes each Codis-Group of the Codis cluster by using a data synchronization task until the whole cluster is synchronized. In this step, enter the ECS instance ID for the master node of Codis-Group 1. When you configure the data synchronization task for Codis-Group 2, enter the ECS instance ID for the master node of Codis-Group 2. You can configure data synchronization tasks for all Codis-Groups by following the procedure described in this topic. Database Type The value of this parameter is set to Redis. Instance Mode The mode of the instance. Select Standalone.Note You must select Standalone for this parameter because data from a Codis cluster cannot be synchronized at a time. DTS synchronizes each Codis-Group of the cluster in a data synchronization task until all Codis-Groups are synchronized. Port Number The service port number of the master node in the Codis-Group. Database Password The database password of the master node.Note This parameter is optional and can be left empty if no database password is set. Destination Instance Details Instance Type The type of the destination database. Select Redis Instance. Instance Region The destination region that you selected on the buy page. You cannot change the value of this parameter. Instance ID The ID of the destination ApsaraDB for Redis instance. Database Password The database password of the ApsaraDB for Redis instance.Note The database password is in the <user>:<password> format. For example, if the username of the account that you use to log on to the source instance is admin and the password is Rp829dlwa, the database password is admin:Rp829dlwa.
- In the lower-right corner of the page, click Set Whitelist and Next. Note
- You do not need to modify the security settings for ApsaraDB instances (such as ApsaraDB RDS for MySQL and ApsaraDB for MongoDB) and ECS-hosted databases. DTS automatically adds the CIDR blocks of DTS servers to the whitelists of ApsaraDB instances or the security group rules of Elastic Compute Service (ECS) instances. For more information, see Add the CIDR blocks of DTS servers to the security settings of on-premises databases.
- After data synchronization is complete, we recommend that you remove the CIDR blocks of DTS servers from the whitelists or security groups.
- Select the processing mode of conflicting tables and the objects to synchronize.
Setting Description Select the processing mode of conflicting tables DTS synchronizes each Codis-Group of the Codis cluster in a data synchronization task until the whole cluster is synchronized. When you configure data synchronization for Codis-Group 1, if the ApsaraDB for Redis instance has no data, select Pre-check and Intercept. When you configure data synchronization for Codis-Groups 2 to N, select Ignore. Otherwise, errors may occur during data synchronization.Note
- Pre-check and Intercept: checks whether the destination database is empty. If the destination database is empty, the precheck is passed. If the destination database is not empty, an error is returned during the precheck and the data synchronization task cannot be started.
- Ignore: skips the precheck for empty destination databases and continues with data synchronization. If the keys in the destination database are the same as those in the source database during data synchronization, the keys in the source database overwrite those in the destination database.
Select objects to be synchronized
- Select one or more databases from the Available section and click to add the databases to the Selected section.
- You can select only databases as the objects to be synchronized. You cannot select keys as the objects to be synchronized.
Rename Databases and Tables The objects to be synchronized. In this scenario, you cannot rename the objects. Replicate Temporary Tables When DMS Performs DDL OperationsIf you use Data Management (DMS) to perform online DDL operations on the source database, you can specify whether to synchronize temporary tables generated by online DDL operations.
- Yes: DTS synchronizes the data of temporary tables generated by online DDL operations. Note If online DDL operations generate a large amount of data, the data synchronization task may be delayed.
- No: DTS does not synchronize the data of temporary tables generated by online DDL operations. Only the original DDL data of the source database is synchronized. Note If you select No, the tables in the destination database may be locked.
Retry Time for Failed ConnectionsBy default, if DTS fails to connect to the source or destination database, DTS retries within the next 720 minutes (12 hours). You can specify the retry time based on your needs. If DTS reconnects to the source and destination databases within the specified time, DTS resumes the data synchronization task. Otherwise, the data synchronization task fails.Note When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time based on your business needs. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released.
- In the lower-right corner of the page, click Next.
- Select the initial synchronization types. Note The value is set to Include full data + incremental data and cannot be changed. DTS synchronizes historical data from the source Codis cluster to the destination Redis databases, and then synchronizes incremental data.
- In the lower-right corner of the page, click Precheck. Note
- Before you can start the data synchronization task, DTS performs a precheck. You can start the data synchronization task only after the task passes the precheck.
- If the task fails to pass the precheck, click the icon next to each failed item to view details.
- After you troubleshoot the issues based on the causes, run a precheck again.
- If you do not need to troubleshoot the issues, ignore failed items and run a precheck again.
- Close the Precheck dialog box after the following message is displayed: Precheck Passed. Then, the data synchronization task starts.
- Wait until initial synchronization is complete and the data synchronization task enters the Synchronizing state. Note You can view the status of the data synchronization task on the Synchronization Tasks page.
- Create and configure a data synchronization task for the other Codis-Group by repeating Steps 1 to 13.
In this topic, the Codis cluster consists of two Codis-Groups. You must create two data synchronization tasks. The following figure shows that the initial synchronization is complete for both tasks and both tasks are in the Synchronizing state.
In this topic, databases DB0 and DB1 are synchronized. You can use Data Management (DMS) to log on to the ApsaraDB for Redis instance and check the total number of keys in the ApsaraDB for Redis instance. The total number of keys is the same as that in the source Codis cluster. For more information about how to use DMS to log on to an ApsaraDB for Redis instance, see Log on to an ApsaraDB for Redis instance by using DMS.