-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replication (snapshot and live) from one Elasticache Redis to another is failing #107
Comments
@nfayzullaev did you manage to solve the issue? The tool works on a smaller DB (4GB in staging), but fails around 6GB (15GB in prod).
|
In my environment, I also encountered the same problem as you. Through testing, I found that the reason is that there are hot keys and large keys in the source DB, which makes riot unable to normally listen ; This is why OOM; |
Hello,
I'm running the following command to replicate from 1 Elasticache cluster to another:
JAVA_OPTS="-Xmx64g" ./riot-redis -i --stacktrace -h source.cache.amazonaws.com -p 6379 replicate -h target.cache.amazonaws.com -p 6379 --batch 1
Source cluster INFO output:
Target cluster INFO output:
The process gets stuck at 31% and never completes.
Typical message is as follows:
Sometimes I see the following stacktrace error:
During live replication (
--mode live
), I'm getting the following error:Source & Target cluster both have 2 nodes in the replication group - each one with 16 CPUs & 64GB RAM.
Replication instance has 32 CPUs & 128GB RAM.
I tried with many-many options (played around with different
--batch
sizing, added--no-verify
,--skip-policy=ALWAYS
, multiple threads) - however nothing is working. Wondering if you can take a look and help me.Thank you,
Nodir
The text was updated successfully, but these errors were encountered: