This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
retry device resync doesn't follow exponentially back off algorithm #9603
Labels
A-Federation
A-Performance
Performance, both client-facing and admin-facing
S-Minor
Blocks non-critical functionality, workarounds exist.
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Description
As far as I'm aware matrix-synapse should stop syncing to dead servers using an exponential back off algorithm.
Reference:
#4979
#5113
This actually doesn't happen if the error is "No Content-Type header received from remote server". Most likely the server owner disabled the server and left the reverse proxy online or the domain got resold and now there is another HTTP/HTTPS service on that domain.
In my case my server tries to contact it almost twice a minute and is spamming my logs. The exponential back off algorithm does not work in that case.
Logs in my case:
Steps to reproduce
Version information
Version: 1.29.0+buster1
Install method: Debian Package Manager
The text was updated successfully, but these errors were encountered: