Redis disconnected slaves incident

Back to Runbooks


This incident type refers to an issue with Redis where one or more slave instances have become disconnected, resulting in replication failure. This can cause data inconsistencies and may require immediate attention to restore normal functioning. The incident may be caused by a variety of factors, such as network issues, server failures, or misconfiguration.



Check if Redis is running

Check Redis logs for any errors

Check Redis replication status

Check number of connected slaves

Check Redis latency

Check network connectivity to Redis instance

Check if Redis instance is listening on the correct port

Check Redis configuration file for any issues

Check resource utilization of Redis instance


Get the Redis instance name

Check the replication status

Identify the disconnected slaves

Restart the Redis server and monitor the replication status.

Manually replicate the data from the master to the disconnected slaves.

Learn more

Related Runbooks

Check out these related runbooks to help you debug and resolve similar issues.