This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Synapse is not limiting the number of EDUs in a transaction #3951
Comments
richvdh
added a commit
that referenced
this issue
Mar 1, 2019
In order to reduce the number of outgoing federation transactions, we want to aggregate read-receipts, since there is little harm if outgoing RRs are delayed by a few seconds, and we can dramatically reduce the number of transactions by doing so. This change introduces the concept of EDU 'buckets'; currently we have the 'Instant' bucket and the 'Delayed' bucket. Fixes #4730, #3951.
@richvdh Was this handled? |
Not really, I'm afraid. The original solution to #4730 got thrown away, and it's still possible for synapse to spam out more than 100 EDUs in a transaction. |
This is fairly urgent imo now that #4513 is a thing - servers cannot federate with each other because the transactions are being turned away. |
I am currently encountering the problem described by @turt2live :
The problem doesn't seem to disappear by itself. How can I tell to my server to put less EDUs in its request? |
3 tasks
richvdh
pushed a commit
that referenced
this issue
May 9, 2019
Fixed by #5138 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It looks like #3805 tries to, however there's some evidence that the EDU limiting doesn't work:
(EDUs are 'dropped' because of a change on t2bot.io - this doesn't change the number of EDUs received from matrix.org)
The text was updated successfully, but these errors were encountered: