Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If an event takes ages to persist it blocks other events from being notified #16633

Open
matrixbot opened this issue Dec 21, 2023 · 0 comments
Open

Comments

@matrixbot
Copy link
Collaborator

matrixbot commented Dec 21, 2023

This issue has been migrated from #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.

@matrixbot matrixbot changed the title Dummy issue If an event takes ages to persist it blocks other events from being notified Dec 22, 2023
@matrixbot matrixbot reopened this Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant