element-hq / element-hq/synapse
If an event takes ages to persist it blocks other events from being notified
Open
O-Occasional
S-Major
T-Defect
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 600
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 51
Description
This issue has been migrated from [#16633](https://github.com/matrix-org/synapse/issues/16633).
---
This is because we assign a stream ordering fairly early on, and we block notifying `/sync` streams / replication / etc about later events until the slow event has finished persisting.
One mitigation could be to assign a stream ordering as late as possible inside the transaction, to minimise the number of queries that could block future events.
Contributor guide
Assessment
This issue has not been assessed yet.