This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Avoid sending massive replication updates when purging a room. #16510
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
clokep
commented
Oct 17, 2023
Co-authored-by: Erik Johnston <[email protected]>
…into clokep/repl-purge
erikjohnston
approved these changes
Oct 18, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When purging a room it doesn't make sense to send every individual update, we can combine them into a "all state is invalid for this room".
As it is hard to mark the room as "being purged" we do this whenever there's many state updates in the room. This should also cover any other unforeseen replication updates with massive amounts of state.