You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to use RIOT's live replication feature to migrate from self-hosted Redis to AWS Elasticache via a read-only replica to avoid performance issues caused by database load.
Our self-hosted Redis database uses standard asynchronous replication with a single writer and a replica. We do not use Redis Cluster.
graph LR;
subgraph self-hosted
subgraph src
src_ro[("src:ro")]
src_rw[("src:rw")]
src_rw -.redis-repl .-> src_ro
end
end
subgraph aws
subgraph dst
dst_rw[(dst:rw)]
end
end
src -. riot-repl .-> dst_rw
Loading
We were able to set up live replication from src:ro, the read-only replica, to dst:rw.
> riot <src:ro> replicate --mode live <dst:rw>
This seems to work well; after writes to src:ro are replicated from src:rw via standard Redis replication, RIOT replicates them to dst:rw.
However, it appears that you cannot restart Redis replication on the replica (src:ro) without RIOT (unexpectedly?) missing writes. Specifically, we observed that writes made to src:rw while replication was paused were not propagated to dst:rw even after Redis replication has replicated them to src:ro.
Could you please clarify whether this behavior is expected
The text was updated successfully, but these errors were encountered:
We want to use RIOT's live replication feature to migrate from self-hosted Redis to AWS Elasticache via a read-only replica to avoid performance issues caused by database load.
Our self-hosted Redis database uses standard asynchronous replication with a single writer and a replica. We do not use Redis Cluster.
We were able to set up live replication from
src:ro
, the read-only replica, todst:rw
.This seems to work well; after writes to
src:ro
are replicated fromsrc:rw
via standard Redis replication, RIOT replicates them todst:rw
.However, it appears that you cannot restart Redis replication on the replica (
src:ro
) without RIOT (unexpectedly?) missing writes. Specifically, we observed that writes made tosrc:rw
while replication was paused were not propagated todst:rw
even after Redis replication has replicated them tosrc:ro
.Could you please clarify whether this behavior is expected
The text was updated successfully, but these errors were encountered: