MatrixSynapse/synapse
Erik Johnston a6ea1a957e
Don't pull event from DB when handling replication traffic. (#8669)
I was trying to make it so that we didn't have to start a background task when handling RDATA, but that is a bigger job (due to all the code in `generic_worker`). However I still think not pulling the event from the DB may help reduce some DB usage due to replication, even if most workers will simply go and pull that event from the DB later anyway.

Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>
2020-10-28 12:11:45 +00:00
..
_scripts
api
app
appservice
config
crypto
events
federation
groups
handlers
http
logging
metrics
module_api
push
replication Don't pull event from DB when handling replication traffic. (#8669) 2020-10-28 12:11:45 +00:00
res/templates
rest Add admin API to list users' local media (#8647) 2020-10-27 14:12:31 +00:00
server_notices
spam_checker_api
state
static
storage Don't pull event from DB when handling replication traffic. (#8669) 2020-10-28 12:11:45 +00:00
streams
util
__init__.py
event_auth.py
notifier.py Don't pull event from DB when handling replication traffic. (#8669) 2020-10-28 12:11:45 +00:00
python_dependencies.py
secrets.py
server.py
types.py
visibility.py