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
Pagination requests can also be handled, but all requests for a given room must be routed to the same instance. Additionally, care must be taken to ensure that the purge history admin API is not used while pagination requests for the room are in flight
This is to ensure that multiple /backfill requests don't happen for the same room concurrently, and that we don't cause confusion by backfilling content that is currently being purged.
To relax this requirement we would need to replace the in-process locks with cross-process locks. We have some such basic locks already for the federation inbound event queues that we could probably reuse
The text was updated successfully, but these errors were encountered:
This issue has been migrated from #11717.
From workers.md:
This is to ensure that multiple
/backfill
requests don't happen for the same room concurrently, and that we don't cause confusion by backfilling content that is currently being purged.To relax this requirement we would need to replace the in-process locks with cross-process locks. We have some such basic locks already for the federation inbound event queues that we could probably reuse
The text was updated successfully, but these errors were encountered: