-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
"stream federation has fallen behind" + a bunch of user IDs #4388
Comments
There is a method that just keeps a list of 11k user IDs around in memory? Is that intentional? |
as a point of interest: I just had a very similar explosion for a different stream and moderately different result set. Synapse appears to have been doing state resolution on an IRC-bridged room and discovered a few thousand unhandled membership events, which is promptly shoved through replication. This blew out the fwiw, the act of dumping the cache into the log filled 5gb of logs in roughly 5 minutes before the entire homeserver was restarted to speed up the resolution of the problem. The server operated fine after being restarted. |
I've facing the same error, but a restart doesn't help. After a few minutes the same show starts again and the service is dead. |
This has definitely gotten worse for me in the last few days: seeing it nearly every 4ish hours. Also seems to have a 50% chance of murdering the homeserver in the most violent way possible: leaving the process running but otherwise non-functional. Applies to presence streams, events, federation, and pretty much everything else. |
Unknown cause, happened on t2bot.io within 15 minutes of startup.
Much shorter errors followed in hoards afterwards:
Reporting because it's Not Good to have ~23k user IDs dropped in a log file for what looks like a Bad Thing. As far as I can tell, everything recovered cleanly after a couple minutes.
The text was updated successfully, but these errors were encountered: