RedisFullCheck icon indicating copy to clipboard operation
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).

Results 53 RedisFullCheck issues
Sort by recently updated
recently updated
newest added

scan系列返回的cursor可能大于等于9223372036854775808, 造成 `cursor, err = strconv.Atoi(string(bytes))` 返回错误。

发布 release artifact 的流水线能否考虑修改一下,支持多架构(如 arm) ``` cd src/full_check GOOS=darwin GOARCH=amd64 $run_builder -ldflags "-X $info" -o "$output/darwin_amd64/redis-full-check" GOOS=darwin GOARCH=arm64 $run_builder -ldflags "-X $info" -o "$output/darwin_arm64/redis-full-check" GOOS=linux GOARCH=amd64 $run_builder -ldflags "-X $info"...

请问能否指定database进行数据对比?比如说只对比db0,

1.下载了最新版本安装包: redis-full-check-1.4.10.tar.gz 2.解压后,./redis-full-check.linux --help 报如下错误: ./redis-full-check.linux: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by ./redis-full-check.linux) ./redis-full-check.linux: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by ./redis-full-check.linux) 3. 安装了GLIBC_2.28 和GLIBC_2.34后,再次运行./redis-full-check.linux --help 依然报错: ./redis-full-check.linux: /lib64/libc.so.6:...

panic: run PipeRawCommand with commands[type key:{06S}:000085389141; type key:{06S}:000094471288; type key:{06S}:000047206801; type key:{06S}:000038639760; type key:{06S}:000027092302; type key:{06S}:000065903103; type key:{06S}:000070559570; type key:{06S}:000029782345; type key:{06S}:000099536077; type key:{06S}:000041388060; type key:{06S}:000094407227; type key:{06S}:000000329824; type key:{06S}:000072597388;...

connection not working if password contains colon ":" example password "123:3333:444" user: "default" --sourcepassword 'default:123:3333:444' I fixed it on client side https://github.com/tair-opensource/RedisFullCheck/compare/develop...azhurbilo:RedisFullCheck:fix_password_with_colon but later noticed that the same issue in...

如下图所示,使用下面命令进行两个集群的比较 ./redis-full-check -s "192.168.0.239:6379;192.168.0.59:6379;192.168.0.21:6379" --sourcedbtype=1 -t "192.168.0.178:6379;192.168.0.142:6379;192.168.0.190:6379" --targetdbtype=1 -p 123qwe,. -a 123qwe,. --comparemode=1 ![image](https://github.com/tair-opensource/RedisFullCheck/assets/50097381/24fea216-0da3-4e8b-97b2-4d258a7537e5)

**问题描述:** 同一批个数据存在于redis-cluster 和redis 主从db5 数据源中,在进行源数据和目标数据进行比对时,源数据中的所有数据都被标记有问题数据,且sqlite3 输出结果 中conflict_type = lack_target (key在源数据库中,不在目的数据库中) **问题背景:** 源redis 配置: 1. redis-cluster 集群模式6主6从 目标redis 配置: 1. 单机redis ,数据源在db5 redis-full-check 版本 1.4.8 比对模式: FullValue **比对需求: 比对源redis-cluster 模式 指定key...