-
Notifications
You must be signed in to change notification settings - Fork 237
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
Add locking to more safely delete state groups: Part 1 #18107
Open
erikjohnston
wants to merge
7
commits into
develop
Choose a base branch
from
erikj/state_epochs2
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
erikjohnston
force-pushed
the
erikj/state_epochs2
branch
3 times, most recently
from
January 24, 2025 16:27
19c8e98
to
53a7438
Compare
erikjohnston
changed the title
Add locking to more safely delete state groups
Add locking to more safely delete state groups: Part 1
Jan 29, 2025
erikjohnston
force-pushed
the
erikj/state_epochs2
branch
2 times, most recently
from
January 29, 2025 11:18
4938211
to
379c0f7
Compare
Currently we don't really have anything that stops us from deleting state groups when an in-flight event references it. This is a fairly rare race currently, but we want to be able to more aggresively delete state groups so it is important to address this to ensure that the database remains valid. See the class docstring of the new data store for an explanation for how this works.
erikjohnston
force-pushed
the
erikj/state_epochs2
branch
from
January 29, 2025 11:48
379c0f7
to
4495545
Compare
devonh
reviewed
Jan 29, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new tables & logic all makes sense to me. Just a couple of tidying up tasks to do.
synapse/storage/schema/state/delta/89/01_state_groups_deletion.sql
Outdated
Show resolved
Hide resolved
Co-authored-by: Devon Hudson <[email protected]>
Co-authored-by: Devon Hudson <[email protected]>
devonh
reviewed
Jan 31, 2025
devonh
reviewed
Jan 31, 2025
synapse/storage/schema/state/delta/89/01_state_groups_deletion.sql
Outdated
Show resolved
Hide resolved
devonh
approved these changes
Jan 31, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple more small comment tweaks then this is good to go!
Co-authored-by: Devon Hudson <[email protected]>
….sql Co-authored-by: Devon Hudson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently we don't really have anything that stops us from deleting state groups when an in-flight event references it. This is a fairly rare race currently, but we want to be able to more aggressively delete state groups so it is important to address this to ensure that the database remains valid.
This implements the locking, but doesn't actually use it.
See the class docstring of the new data store for an explanation for how this works.