RedisFullCheck
RedisFullCheck copied to clipboard
redis-full-check is used to compare whether two redis have the same data. Support redis version from 2.x to 7.x (Don't support Redis Modules).
zsh: exec format error: ./redis-full-check ./redis-full-check -t 127.0.0.1:6379 -s 127.0.0.1:6679
云环境不支持hgetall命令导致报错
[root@iZs7z01dz0z12dyttz9zn5Z redis-full-check-1.4.8]# ./redis-full-check -s "10.252.120.10:8004;10.252.120.8:8002;10.252.120.9:8003;10.252.120.7:8001;10.252.120.11:8006;10.252.120.12:8005" -t "10.252.120.7:9001;10.252.120.8:9002;10.252.120.9:9003;10.252.120.10:9004;10.252.120.11:9006;10.252.120.12:9005" --comparemode=1 --comparetimes=1 --qps=10 --batchcount=100 --targetdbtype=1 [INFO 2021-06-22-15:10:37 main.go:65]: init log success [ERROR 2021-06-22-15:10:37 main.go:105]: source address[10.252.120.10:8004;10.252.120.8:8002;10.252.120.9:8003;10.252.120.7:8001;10.252.120.11:8006;10.252.120.12:8005] illegal[if type isn't cluster, should only used...
[root@iZs7z01dz0z12dyttz9zn5Z redis-full-check-1.4.7]# ./redis-full-check -s "10.252.120.7:8001;10.252.120.8:8002;10.252.120.9:8003;10.252.120.10:8004;10.252.120.11:8006;10.252.120.12:8005" -t "10.252.120.7:9001;10.252.120.8:9002;10.252.120.9:9003;10.252.120.10:9004;10.252.120.11:9006;10.252.120.12:9005" --comparemode=1 --comparetimes=1 --qps=10 --batchcount=100 --sourcedbtype=1 --targetdbtype=1 --targetdbfilterlist=0 [INFO 2021-06-22-10:54:09 main.go:65]: init log success [INFO 2021-06-22-10:54:09 main.go:164]: configuration: {10.252.120.7:8001;10.252.120.8:8002;10.252.120.9:8003;10.252.120.10:8004;10.252.120.11:8006;10.252.120.12:8005 auth 1 -1 10.252.120.7:9001;10.252.120.8:9002;10.252.120.9:9003;10.252.120.10:9004;10.252.120.11:9006;10.252.120.12:9005 auth...
redis-full-check能支持redis-cluster主从之间的数据对比嘛?试验了一下好像是有点问题的,假如支持需要怎么做呢?还有是否支持某一时间段的对比
请问redisfullcheck 现在支持redis6吗, 如果不支持话,有没有相关计划。
1: client/client.go文件,PipeLenCommand函数中,若批量获取长度返回错误时,在else语句块中,应该将result[i]设为-1,而非返回错误; 2: 建议取消对sqlite的依赖,用目标redis的实例来暂存中间结果。
场景: 源db数据在db 0,目标db数据在db1 执行命令和输出结果如下: ./redis-full-check -t 10.129.104.13:30205 -s 10.129.104.13:30971 --result total_result --targetdbfilterlist=1 --comparemode=3 --sourcedbfilterlist=0 [INFO 2020-03-25-12:40:18 main.go:65]: init log success [INFO 2020-03-25-12:40:18 main.go:168]: configuration: {10.129.104.13:30971 auth 0 0 10.129.104.13:30205 auth...
用户源端有183个key,目标端有179个key,除去DTS参数外有4个丢失了,full-check校验也的确是缺失了4个key,但是显示的key字段丢失,且类型字段的string中的s丢失了。 