Preventing Pipeline Calls from Crashing Redis Clusters

This post details an investigation into a Redis cluster outage caused by a single slave node failure. It explains how the Go-Redis client's pipeline error handling and one-minute state refresh interval contributed to a prolonged service disruption. The post identifies that a single command failure within a pipeline could cause the entire pipeline to fail and that the client's state refresh delay led to continued attempts to contact unreachable nodes. It also clarifies that write queries were unaffected due to master node direct routing and client-side monitoring.