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

More AssertionErrors from replication_notifier #7340

Closed
richvdh opened this issue Apr 24, 2020 · 3 comments · Fixed by #7636
Closed

More AssertionErrors from replication_notifier #7340

richvdh opened this issue Apr 24, 2020 · 3 comments · Fixed by #7636
Assignees
Labels
A-Workers Problems related to running Synapse in Worker Mode (or replication)

Comments

@richvdh
Copy link
Member

richvdh commented Apr 24, 2020

we have a function db_query_to_update_function which wraps a database query function so that it can be used as an update_function for replication streams. It relies on the wrapped function returning no more than the number of rows asked for. #7337 found and fixed one instance where this was not the case, but we should check if there are any more.

@richvdh
Copy link
Member Author

richvdh commented Apr 29, 2020

as per #7351 (comment), at least the federation and account_data streams are broken. I think we should just go through each of the streams and check their behaviour, before this stuff bites us again.

@richvdh richvdh changed the title check that things using db_query_to_update_function honour the limit More AssertionErrors from replication_notifier Apr 29, 2020
@babolivier
Copy link
Contributor

babolivier commented May 4, 2020

Removing the release blocker label as #7378 mitigates it, though I'm leaving this issue open as it looks like it needs more investigation.

@erikjohnston
Copy link
Member

#7740 has cleaned this up a lot

@richvdh richvdh added the A-Workers Problems related to running Synapse in Worker Mode (or replication) label Feb 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Workers Problems related to running Synapse in Worker Mode (or replication)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants