Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

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

Open
erikjohnston opened this issue Nov 14, 2023 · 2 comments
Labels
O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Major functionality / product severely impaired, no satisfactory workaround. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues.

Comments

@erikjohnston
Copy link
Member

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.

@clokep
Copy link
Contributor

clokep commented Nov 20, 2023

@erikjohnston did one of your recent PRs fix this?

@clokep clokep added S-Major Major functionality / product severely impaired, no satisfactory workaround. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. O-Occasional Affects or can be seen by some users regularly or most users rarely labels Nov 20, 2023
@erikjohnston
Copy link
Member Author

@erikjohnston did one of your recent PRs fix this?

Alas not, no. (I think we fixed an underlying cause of slow persists, maybe? But not this issue itself)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Major functionality / product severely impaired, no satisfactory workaround. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Projects
None yet
Development

No branches or pull requests

2 participants