A recovery re-reads a link that keeps failing while a ready standby waits #65
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
cmoriarty/sports-breaker#65
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
A failed stream's recovery always starts by re-reading the same link (
Channel._recover, step 1). If the page still yields a stream, the channel lands on it again, however often that link has just failed. The ready standby is only tried when the re-read finds nothing.Seen live, 2026-10-31, Chelsea vs. Man Utd (UTC)
Decided
Re-read the link first as now (a fresh read often fixes an expired token), unless that link already needed a recovery in the last 5 minutes. Then the ready standby comes first, and the link cools as a swapped-out link does. This was my recommended default; the operator didn't choose otherwise when the batch was set up.
Deployed 2026-10-31 17:44 UTC (PR #67,
1938e97). Left open until a relapse is seen live.Done when a channel's history shows "recovered on ( failed again within 5 min)". That needs a link that fails twice within five minutes while a standby is ready, so it can't be forced.
Closed on the tests at the operator's word (2026-11-01): reopen, or file a new ticket, if production shows a problem.