Hot shard in Redis Cluster
A celebrity posted at 20:00 and one piece of content is going viral. Your Redis Cluster spreads keys across 12 shards, but one shard's CPU is at 100% while the other 11 sit at 20%, that shard's network egress is saturated, and reads of the viral post's cached payload are timing out even though the data is cached and small. Overall cluster memory is fine. How do you triage and mitigate this in real time?
What a strong answer looks like
Stop the bleeding first (mitigate), then form hypotheses from real signals. Separate root cause from symptom, communicate status as you go, and close with what prevents a repeat.
0:00 of about 35 min
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.