-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Server DoSed by incoming 'groups' federation requests #5933
Comments
And here is not rate-limited
and more than 1600 same |
yes, looks like the groups code does not handle 429s (or failures of any kind) gracefully.
Looking at these from the matrix.org end, all of them seem to end with a timeout or a 429. I can't really suggest much except to stop using groups until the functionality is more mature. Related #2654 |
@richvdh Thanks for describing!
Can you describe easier way to force stop using groups on homeserver, especially for not broke federation? Manually clean-up Or maybe simply block |
So, I blocked groups queries in nginx proxy via this rule:
|
This comment has been minimized.
This comment has been minimized.
Communities/groups are being removed, see #11584. |
My ru-matrix.org homeserver very often do rate limiting to incoming federation requests from matrix.org server, I see a lot of
SynapseError: 429 - Too Many Requests
in logs.Even if I increase limits to:
But when I grep logs, I see that it contains very much
groups
federation requests every second, here is example of one minute range grep from logs (143 queries per minute!):Why those federation requests sends too often, without reacting to 429 error and delaying? I think that this is bug in Synapse, that don't apply rate limiting to outgoing federation requests of
groups
category?The text was updated successfully, but these errors were encountered: