This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Leaving a room can cause you to be hammered with GET /event requests from other servers #4726
Labels
A-Federation
A-Performance
Performance, both client-facing and admin-facing
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Tolerable
Minor significance, cosmetic issues, low or no impact to users.
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Comments
|
it might be useful to hang onto the logs for this, to aid with any potential future investigation. |
|
Logs dumped. Given it might be a while before someone gets around to this, I've dropped them into an invite-only matrix room: #synapse-4762:t2l.io (mentioning this here for when I forget in N months) |
MadLittleMods
added
T-Defect
erikjohnston
added
S-Tolerable
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
And not even for your own events :(
I ran a script to peacefully decommission a homeserver by having it leave all rooms, and shortly after the events went out I was being hammered with GET /event requests for the rooms I just left. Surely I shouldn't be receiving these requests anymore given there's no guarantee that the homeserver even knows about the room anymore?
The text was updated successfully, but these errors were encountered: