redis-cli -h <master-ip> info replication
. Look for the lag
field under each slave to see how far behind each replica is.ping
command between the master and replica instances to check if network latency is contributing to the slow replication.top
or htop
(Linux), Activity Monitor
(Mac), or Task Manager (Windows) to check the usage on both master and replica servers.redis.conf
file or use CONFIG GET
command to check for any misconfiguration, especially the repl-backlog-size
and client-output-buffer-limit slave
settings, which can impact replication.redis-cli -h <master-ip> --latency-history
to monitor command latencies and identify slow commands affecting replication.redis-cli --bigkeys
or MEMORY USAGE <key>
to find and possibly refactor or delete large keys that might be causing replication delays.iostat
(Linux) to monitor disk I/O performance. Slow disks can significantly affect replication speed, especially when dealing with large datasets.SLAVEOF NO ONE
followed by SLAVEOF <master-ip> <master-port>
on the replica. This should be done with caution and ideally during a maintenance window.Let Dr. Droid create custom investigation plans for your infrastructure.
Book Demo