This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Faster joins: check purge behavior is ok when in partial state #14859
Labels
A-Admin-API
A-Federated-Join
joins over federation generally suck
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Minor
Blocks non-critical functionality, workarounds exist.
T-Enhancement
New features, changes in functionality, improvements in performance, or user-facing enhancements.
Milestone
Comments
MatMaul
added
A-Federated-Join
joins over federation generally suck
S-Minor
Blocks non-critical functionality, workarounds exist.
T-Enhancement
New features, changes in functionality, improvements in performance, or user-facing enhancements.
labels
Jan 17, 2023
MatMaul
added this to the Q4 2022: faster joins: worker-mode and remaining work milestone
Jan 17, 2023
DMRobertson
added
A-Admin-API
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
labels
Jan 17, 2023
erikjohnston
modified the milestones:
Q4 2022: faster joins: worker-mode and remaining work,
Remaining faster remote join work
Feb 2, 2023
Testing this locally:
Hooray for constraints. We'll need to delete from the partial state tables. |
This was referenced Feb 13, 2023
I think we consider this closed by #15069. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
A-Admin-API
A-Federated-Join
joins over federation generally suck
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Minor
Blocks non-critical functionality, workarounds exist.
T-Enhancement
New features, changes in functionality, improvements in performance, or user-facing enhancements.
Purging a room with the admin API when we are in partial state should be handled gracefully.
We could reject the purge, or just wait for the full state and then do it.
Second approach is however not restart friendly: if we restart during a resync, the resync process will be resume but the purge will be ignored (? since purge v2 is async, to be checked).
relevant #synapse-dev conversation: https://matrix.to/#/!vcyiEtMVHIhWXcJAfl:sw1v.org/$vCxad2MgGfIiZYJOdscIrR6kY6H0aGc4jzc0MWYzXk4?via=matrix.org&via=element.io&via=envs.net
The text was updated successfully, but these errors were encountered: