> an immediate retry would've ended up going over the same socket and getting the same response This is kind of a big assumption you're making. If you're going

> an immediate retry would've ended up going over the same socket and getting the same response This is kind of a big assumption you're making. If you're going to do retries when a backend is unavailable, explicitly doing it against the same backend is obviously a decision that defeats the entire purpose. > probably also has a latency SLI Then take this into account w.r.t timeouts on internal requests/retries. My point is that this was a problem that was (at least partially) addressable by the team with the impacted SLO, and did not have to wait for someone to fix the root cause in order to improve their situation.