Redis-shake is developed and maintained by NoSQL Team in Alibaba-Cloud Database department.
Redis-shake has made some improvements based on redis-port, including bug fixes, performance improvements and feature enhancements.
The type can be one of the followings:
decode: Decode dumped payload to human readable format (hex-encoding).
restore: Restore RDB file to target redis.
dump: Dump RDB file from source redis.
sync: Sync data from source redis to target redis by sync or psync command. Including full synchronization and incremental synchronization.
rump: Sync data from source redis to target redis by scan command. Only support full synchronization. Plus, RedisShake also supports fetching data from given keys in the input file when scan command is not supported on the source side. This mode is usually used when
psyncredis commands aren’t supported.
Please check out the conf/redis-shake.conf - https://github.com/alibaba/RedisShake/blob/develop/conf/redis-shake.conf to see the detailed parameters description.
Redis-shake has several parameters in the configuration conf/redis-shake.conf, that maybe confusing, if this is your first time using, please visit this tutorial - https://github.com/alibaba/RedisShake/wiki/tutorial-about-how-to-set-up.
User can use RedisFullCheck - https://github.com/alibaba/RedisFullCheck to verify correctness.
Redis-shake offers metrics through restful api and log file.
log: the metric info will be printed in the log periodically if enable.
inner routine heap:
Both the source and target type can be standalone, opensource cluster and proxy. Although the architecture patterns of different vendors are different for the proxy architecture, we still support different cloud vendors like alibaba-cloud, tencent-cloud and so on.
If the target is open source redis cluster, redis-shake uses
redis-go-cluster - https://github.com/chasex/redis-go-cluster driver to write data. When target type is proxy, redis-shakes write data in round-robin way.
If the source is redis cluster, redis-shake launches multiple goroutines for parallel pull. User can use
rdb.parallel to control the RDB syncing concurrency.
move slot operations must be disabled on the source side.
You can directly download the binary in the release package - https://github.com/alibaba/RedisShake/releases. Run through similar commands:
./redis-shake.linux -type=sync -conf=redis-shake.conf # please note: user must modify redis-shake.conf first to match needs.
restore key[x:x] error[MOVED xxxx when target to Alibaba Cloud KVStore
[PANIC] dbRumper executor restore key[a:a] error[MOVED 6060 172.16.1.100:6379]: pttl, value length, rdb version, checksum, check error[<nil>]
(TODO) May be the Redis version between source and target is not compatible。
Target key name already exists
[PANIC] dbRumper executor restore key[a:a] error[BUSYKEY Target key name already exists.]: pttl, value length, rdb version, checksum, check error[<nil>]
rewrite to fix that issue.
 alibaba/RedisFullCheck: redis-full-check is used to compare whether two redis have the same data. redis-full-check用于比较2个redis数据是否一致，支持单节点、主从、集群版、以及多种proxy，支持同构以及异构对比，redis的版本支持2.x-5.x。 - https://github.com/alibaba/RedisFullCheck