summary refs log tree commit diff
path: root/synapse/crypto
diff options
context:
space:
mode:
authorErik Johnston <erik@matrix.org>2017-10-03 11:09:51 +0100
committerErik Johnston <erik@matrix.org>2017-10-03 11:18:21 +0100
commit30848c0fcd34aaf0b2db7b65c91648ae49c480a2 (patch)
tree0f759f262edfd52355541385854d6ad7f2e03b26 /synapse/crypto
parentMerge branch 'master' of github.com:matrix-org/synapse into develop (diff)
downloadsynapse-30848c0fcd34aaf0b2db7b65c91648ae49c480a2.tar.xz
Ignore incoming events for rooms that we have left
When synapse receives an event for a room its not in over federation, it
double checks with the remote server to see if it is in fact in the
room. This is done so that if the server has forgotten about the room
(usually as a result of the database being dropped) it can recover from
it.

However, in the presence of state resets in large rooms, this can cause
a lot of work for servers that have legitimately left. As a hacky
solution that supports both cases we drop incoming events for rooms that
we have explicitly left.

This means that we no longer support the case of servers having
forgotten that they've rejoined a room, but that is sufficiently rare
that we're not going to support it for now.
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions