This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Synapse potentially cached a failed sync request #9507
Labels
S-Major
Major functionality / product severely impaired, no satisfactory workaround.
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
X-Regression
Something broke which worked on a previous release
X-Release-Blocker
Must be resolved before making a release
Running 4a32600
Last night my database suffered an issue which meant that it was briefly unavailable, and it dropped all connections for a period. Synapse seemed to largely recover as sync requests to some accounts are working, and federation/event creation seems to be working fine.
(ignore the absolutely awful sync duration, it's sadly a new normal atm)
However, sync requests for my Element android device fail with a 500 each time:
Given that I am 100% certain that my other devices are actively getting new events and hitting the DB successfully on the same process, I am confused as to why the Element android device might be seeing this over and over. It feels like the failure was cached, especially due to the quick response time.
The text was updated successfully, but these errors were encountered: