MatrixSynapse/synapse/replication/tcp
Richard van der Hoff ce428a1abe Fix EventsStream raising assertions when it falls behind
Figuring out how to correctly limit updates from this stream without dropping
entries is far more complicated than just counting the number of rows being
returned. We need to consider each query separately and, if any one query hits
the limit, truncate the results from the others.

I think this also fixes some potentially long-standing bugs where events or
state changes could get missed if we hit the limit on either query.
2020-04-24 13:59:21 +01:00
..
streams Fix EventsStream raising assertions when it falls behind 2020-04-24 13:59:21 +01:00
__init__.py Move client command handling out of TCP protocol (#7185) 2020-04-06 09:58:42 +01:00
client.py Add ability to run replication protocol over redis. (#7040) 2020-04-22 13:07:41 +01:00
commands.py Stop the master relaying USER_SYNC for other workers (#7318) 2020-04-22 22:39:04 +01:00
handler.py Stop the master relaying USER_SYNC for other workers (#7318) 2020-04-22 22:39:04 +01:00
protocol.py Fix replication metrics when using redis (#7325) 2020-04-22 16:26:19 +01:00
redis.py Fix replication metrics when using redis (#7325) 2020-04-22 16:26:19 +01:00
resource.py Move server command handling out of TCP protocol (#7187) 2020-04-07 10:51:07 +01:00