RedisFullCheck

Redis-full-check is used to compare whether two redis have the same data. We also offer a data synchronization tool called redis-shake to syncing data from one redis to another redis.

Thanks to the Douyu's WSD team for the support.

• 中文文档
• Download redis-full-check.tar.gz
• 第一次使用，如何进行配置

redis-full-check

---

Redis-full-check is developed and maintained by NoSQL Team in Alibaba-Cloud Database department.

Redis-full-check performs full data verification by comparing the data of the source database and the destination database. The entire check process consists of multiple comparisons, in every comparison, redis-full-check fetches data from two dabatases and then compared, the inconsistent data is put into sqlite3 db for the next comparison. By this iteratively comparing method, the difference continues to converge. The following figure shows the dataflow. In every comparison which is the yellow box, redis-full-check fetches all keys firstly. After that, it runs comparison and stores the difference result(key and field) into the sqlite3 db which is the position that keys and fields can be fetched in next round instead of the source database.

Redis-full-check fetches keys from source and then checks these keys exist on the target. So if one key exists on the target but lack on the source, redis-full-check can't find it. If you want to know whether the data in the source and destination databases are exactly the same, you need to set up a bidirectional link:

• source->RedisFullCheck->target
• target->RedisFullCheck->source

supports

standalone, cluster, proxy(aliyun-cluster, tencent-cluster). Redis version from 2.x to 7.x (Don't support Redis Modules).

Code branch rules

Version rules: a.b.c.

• a: major version
• b: minor version. even number means stable version.
• c: bugfix version

branch name	rules
master	master branch, do not allowed push code. store the latest stable version. develop branch will merge into this branch once new version created.
develop(main branch)	develop branch. all the bellowing branches fork from this.
feature-*	new feature branch. forked from develop branch and then merge back after finish developing, testing, and code review.
bugfix-*	bugfix branch. forked from develop branch and then merge back after finish developing, testing, and code review.
improve-*	improvement branch. forked from develop branch and then merge back after finish developing, testing, and code review.

Tag rules:

Add tag when releasing: "release-v{version}-{date}". for example: "release-v1.0.2-20180628"

Paramters

…

Usage

---

Run ./bin/redis-full-check.darwin64 or redis-full-check.linux64 which is built in OSX and Linux respectively, however, the binaries aren't always the newest version.

Or you can build redis-full-check yourself according to the following steps:

• git clone https://github.com/alibaba/RedisFullCheck.git
• cd RedisFullCheck/
• ./build.sh
• ./bin/redis-full-check -s $(source_redis_ip_port) -p $(source_password) -t $(target_redis_ip_port) -a $(target_password) # these parameters should be given by users

Here comes the sqlite3 example to display the conflict result:

…

Shake series tool

---

We also provide some tools for synchronization in Shake series.

• MongoShake: mongodb data synchronization tool.
• RedisShake: redis data synchronization tool.
• RedisFullCheck: redis data synchronization verification tool.

License

• On 20230427 and later, we distribute this library under the new Apache2.0 protocol, 1.4.10 is the first version to support the Apache2.0 protocol.
• Prior to 20230427, it was distributed under the GPLV3.0 protocol.