source.type |
Yes |
Select a value based on the architecture of the source ApsaraDB for Redis instance.
Valid values:
|
standalone |
source.address |
Yes |
The connection address and port number of the source ApsaraDB for Redis instance.
Separate the connection address and port number with a colon (:). For more information
about how to obtain the connection address and port number of the ApsaraDB for Redis
instance, see View endpoints.
- If you connect an ECS instance to the ApsaraDB for Redis instance through a VPC, you
must obtain the internal endpoint of the ApsaraDB for Redis instance in the VPC.
- If you connect an on-premises machine to the ApsaraDB for Redis instance over the
Internet, you must obtain the public endpoint of the ApsaraDB for Redis instance.
Note If the source ApsaraDB for Redis instance is of cluster architecture, you must connect
to the instance deployed in a VPC by using a private endpoint. You must add the master@ prefix to the connection address, for example, master@r-bp1mfnrflszg75w****.redis.rds.aliyuncs.com:6379 . For more information about how to request a private endpoint, see Enable a direct connection.
|
r-bp1mfnrflszg75w****.redis.rds.aliyuncs.com:6379 |
source.password_raw |
Yes |
The name of the account with Copy permissions and password of the source ApsaraDB for Redis instance. Separate the
account name and password with a colon (:). For more information about how to create
an account, see Create and manage database accounts.
Note Instances of the cluster architecture do not support creating accounts with Copy permissions.To enable this feature, submit a ticket.
|
testaccount:Rp829dlwa |
target.type |
Yes |
Select a value based on the architecture of the destination ApsaraDB for Redis instance.
Valid values:
|
cluster |
target.address |
Yes |
The connection address and port number of the destination ApsaraDB for Redis instance.
Separate the connection address and port number with a colon (:). For more information
about how to obtain the connection address and port number of the ApsaraDB for Redis
instance, see View endpoints.
- If you connect an ECS instance to the ApsaraDB for Redis instance through a VPC, you
must obtain the internal endpoint of the ApsaraDB for Redis instance in the VPC.
- If you connect an on-premises machine to the ApsaraDB for Redis instance over the
Internet, you must obtain the public endpoint of the ApsaraDB for Redis instance.
Note If the destination instance is of cluster architecture, you must connect to the instance
deployed in a VPC by using a private endpoint. You must add the master@ prefix to the connection address, for example, master@r-bp1mfnrflszg75w****.redis.rds.aliyuncs.com:6379 . For more information about how to request a private endpoint, see Enable a direct connection.
|
master@r-bp1mfnrflszg75w****.redis.rds.aliyuncs.com:6379 |
target.password_raw |
Yes |
The name of the account with read and write permissions and password of the destination ApsaraDB for Redis instance. Separate
the account name and password with a colon (:). For more information about how to
create an account, see Create and manage database accounts.
|
testaccount:Rp829dlwa |
target.db |
No |
Specifies whether to migrate data from all databases in the source ApsaraDB for Redis
instance to the specified databases in the destination ApsaraDB for Redis instance.
Valid values:
- -1 (default): disables this feature.
- 0 to 255: enables this feature. The value specifies the destination database in the destination
ApsaraDB for Redis instance. For example, a value of 0 indicates that the data of
all databases in the source ApsaraDB for Redis instance is migrated to database 0
in the destination ApsaraDB for Redis instance.
Note If the source ApsaraDB for Redis instance is of the standard architecture and the destination ApsaraDB for Redis instance is of the cluster architecture, only database 0 is synchronized in this scenario. Data from other databases is not
migrated. Set this parameter to 0 to migrate all the databases from the source ApsaraDB
for Redis instance to database 0 in the destination ApsaraDB for Redis instance.
|
-1 |
key_exists |
No |
The writing policy that is applied when the keys in the source database are the same
as those in the destination database. Valid values:
- rewrite: overwrites the existing keys in the destination database that are the same as those
in the source database.
- none: This is the default value. Redis-shake stops running and a message appears that
indicates conflicting keys.
- ignore: skips the current key, retains the data in the destination database, and continues
migrating data.
|
rewrite |
filter.db.whitelist |
No |
The names of the databases to be migrated. Separate multiple database names with semicolons
(;). The default value is empty, which indicates that all databases are to be migrated.
|
0;1 |
filter.db.blacklist |
No |
The names of databases that do not need to be migrated. This is a blacklist. Separate
multiple database names with semicolons (;). By default, this parameter is not specified
and no blacklist is configured.
|
1;2 |
parallel |
No |
The number of concurrent threads for redis-shake to perform the migration tasks. You
can specify a large value to improve synchronization performance.
Note The default value is 32. The minimum value is 1. The maximum value depends on the
performance of the server where redis-shake is deployed.
|
32 |