You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's possible to query the room directory after the room creation and not see the room.
Reproduction steps
Using monolith Synapse
Create a public room called foo with /createRoom
Immediately after seeing a successful create room response, search the room directory for the room (/publicRooms with { filter: { generic_search_term: 'foo' } })
It seems like we're await'ing everywhere so not sure why this would happen. And seems weird that it would happen in monolith mode since there is not replication lag and we're awaiting everything.
The text was updated successfully, but these errors were encountered:
matrixbot
changed the title
Dummy issue
Race condition with room creation means room directory lacks read-after-write consistency in monolith mode
Dec 21, 2023
This issue has been migrated from #15526.
It's possible to query the room directory after the room creation and not see the room.
Reproduction steps
foo
with/createRoom
/publicRooms
with{ filter: { generic_search_term: 'foo' } }
)If you give the homeserver some time, the room will show up.
Notes
This regressed in matrix-org/synapse#15229 where I guess the timing changed just enough for this to be possible. You can see the full bisect, investigation and context for how I noticed in matrix-org/matrix-viewer#208 (comment)
It seems like we're
await
'ing everywhere so not sure why this would happen. And seems weird that it would happen in monolith mode since there is not replication lag and we're awaiting everything.The text was updated successfully, but these errors were encountered: