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: Update user directory once state re-sync completes #12815
Closed
1 task
Tracked by
#14030
Labels
A-Federated-Join
joins over federation generally suck
T-Task
Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
Milestone
Comments
babolivier
added
the
T-Task
Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
label
May 20, 2022
Also: what does the directory say during re-sync, and is that ok? |
Particular points of note:
|
squahtx
pushed a commit
that referenced
this issue
Jan 19, 2023
When finishing a partial state join to a room, we update the current state of the room without persisting additional events. Workers receive notice of the current state update over replication, but neglect to wake the room stats and user directory updaters, which then get incidentally triggered the next time an event is persisted or an unrelated event persister sends out a stream position update. We wake the room stats and user directory updaters at the appropriate time in this commit. Part of #12814 and #12815. Signed-off-by: Sean Quah <[email protected]>
squahtx
pushed a commit
that referenced
this issue
Jan 19, 2023
When finishing a partial state join to a room, we update the current state of the room without persisting additional events. Workers receive notice of the current state update over replication, but neglect to wake the room stats and user directory updaters, which then get incidentally triggered the next time an event is persisted or an unrelated event persister sends out a stream position update. We wake the room stats and user directory updaters at the appropriate time in this commit. Part of #12814 and #12815. Signed-off-by: Sean Quah <[email protected]>
squahtx
pushed a commit
that referenced
this issue
Jan 19, 2023
When finishing a partial state join to a room, we update the current state of the room without persisting additional events. Workers receive notice of the current state update over replication, but neglect to wake the room stats and user directory updaters, which then get incidentally triggered the next time an event is persisted or an unrelated event persister sends out a stream position update. We wake the room stats and user directory updaters at the appropriate time in this commit. Part of #12814 and #12815. Signed-off-by: Sean Quah <[email protected]>
During re-sync, the user directory reflects the current state of the room and excludes all remote users except new joiners. |
DMRobertson
pushed a commit
that referenced
this issue
Jan 23, 2023
…n finishing join (#14874) * Faster joins: Update room stats and user directory on workers when done When finishing a partial state join to a room, we update the current state of the room without persisting additional events. Workers receive notice of the current state update over replication, but neglect to wake the room stats and user directory updaters, which then get incidentally triggered the next time an event is persisted or an unrelated event persister sends out a stream position update. We wake the room stats and user directory updaters at the appropriate time in this commit. Part of #12814 and #12815. Signed-off-by: Sean Quah <[email protected]> * fixup comment Signed-off-by: Sean Quah <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
A-Federated-Join
joins over federation generally suck
T-Task
Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
Potentially useful / possible blockers:
The text was updated successfully, but these errors were encountered: