MatrixSynapse/synapse/storage
Erik Johnston 026503fa3b
Don't go into federation catch up mode so easily (#9561)
Federation catch up mode is very inefficient if the number of events
that the remote server has missed is small, since handling gaps can be
very expensive, c.f. #9492.

Instead of going into catch up mode whenever we see an error, we instead
do so only if we've backed off from trying the remote for more than an
hour (the assumption being that in such a case it is more than a
transient failure).
2021-03-15 14:42:40 +00:00
..
databases Don't go into federation catch up mode so easily (#9561) 2021-03-15 14:42:40 +00:00
engines
schema
util Refactor to ensure we call check_consistency (#9470) 2021-02-24 10:13:53 +00:00
__init__.py
_base.py
background_updates.py
database.py Refactor to ensure we call check_consistency (#9470) 2021-02-24 10:13:53 +00:00
keys.py
persist_events.py
prepare_database.py
purge_events.py Purge chain cover tables when purging events. (#9498) 2021-03-03 11:04:08 -05:00
push_rule.py Move storage classes into a main "data store". 2019-10-21 16:05:06 +01:00
relations.py
roommember.py Bump the mypy and mypy-zope versions. (#9529) 2021-03-03 07:19:19 -05:00
state.py
types.py