Redis replication broken incident.

Back to Runbooks


This incident type refers to an issue with Redis replication, which means that there is a problem with the synchronization of data between Redis instances. This issue could impact the availability and performance of the system and may require immediate attention to restore the replication and ensure data consistency. The incident could be caused by various factors, such as network problems, hardware failures, or configuration issues. The incident must be investigated and resolved as soon as possible to avoid any data loss or downtime.



Check if Redis is running

Check Redis logs for errors

Verify Redis replication status

Check Redis slave status

Check Redis configuration file

Verify Redis master configuration

Verify Redis slave configuration

Check network connectivity between master and slave

Check network ports for Redis instance

Check Redis replication delay

Network connectivity issues between Redis instances, causing replication failures.


Check the Redis replication configuration to ensure it's correctly set up and that there are no misconfigurations that could cause replication failures.

Verify the Redis version and ensure it's up-to-date with the latest patches and updates.

Learn more

Related Runbooks

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