Closed pamelayin closed 1 year ago
Hi, I tried to replicate your issue with same Redis versions (except redis 6.2.6 container instead of elasticache) but didn't have any error. Would you be able to share a RDB dump?
Hi @jruaux I'm not sure if I can share data directly due to company policy but I was able to reproduce it on redis 6.2.6 using both redis-benchmark and riot generate. It seems like they are both related to the zset data type specifically.
New setup:
node1: redis 4.0.10 container on-premise node2: redis 6.2.6 container on-premise
Testing: same as before but was able to reproduce it with riot generate as well
Error 1 - set(long)
riot <node1> generate --types=zset --count 10000
riot <node1> replicate <node2> --mode live
riot <node2> replicate <node1> --mode live --type ds
Error2 - input string "OK"
riot <node1> generate --types=zset --count 30000
riot <node1> replicate <node2> --mode live
riot <node2> replicate <node1> --mode live --type ds
This testing was done with same riot version as before (v3.1.3). Hope this is enough info to reproduce the error on your end.
This was due to a bug in Lettuce which has been fixed in their latest release. Latest RIOT release (3.1.5) was upgraded to that Lettuce release.
Hi, currently I'm testing out Riot as migration tool from Redis to Elasticache and also the other way around (for fallback).
I'm running into 2 separate errors for the fallback. Setup and errors are described below.
Setup On-prem redis: version 4.0.10 standalone Elasticache: version 6.2.6 standalone Riot: version v3.1.1 on AWS EC2 instance (OS: Amazon Linux 2) Data generation: tried with both
riot generate
with --types=hash,list,set,sorted set, string andredis-benchmark
-t zadd,hset,rpush,sadd,setFirst data has been replicated from on-prem Redis to Elasticache via
riot <onprem source> replicate <elasticache target> --mode live
. Then doing fallback usingriot <elasticache source> replicate <onprem target> --mode live --type ds
. The errors are produced during the fallback step.Errors
Encountered an error executing step scan-step in job replicate-job: io.lettuce.core.output.StatusOutput does not support set(long)
data generation:
redis-benchmark <onprem redis> -t zadd,hset,rpush,sadd,set -r 10000 -q -n 10000
stack trace:
Is it really that there's limitation in replicating set data types or is it caused by another issue?
Encountered an error executing step scan-step in job replicate-job: For input string: "OK"
data generation:
redis-benchmark <onprem redis> -t zadd,hset,rpush,sadd,set -r 1000 -q -n 10000
thenredis-benchmark <onprem redis> -t zadd,hset,rpush,sadd,set -r 10000 -q -n 10000
stack trace:
Is this actual bug or some condition I can get around otherwise?