This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Retry schedule inexplicably resets on down hosts #5414
Comments
here's another weirdness from v1.0.0-rc1:
Despite declaring 'backoff now 86400000', it promptly then starts a new retry cycle on a new transaction immediately afterwards :| |
key lookups are exempt from the backoff, so I don't think the retry schedule is actually being reset here. Hence, closing in favour of #5413 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Looking into why synapse tries to hammer dead hosts, grepping strictly for
matrix.breaker.rocks
(which doesn't even exist in DNS), I see:It's very unclear as to why the backoff keeps resetting to 0.
This particular log sequence was on 0.99.3 or 0.99.4.
(xref #1404)
The text was updated successfully, but these errors were encountered: