This repository was archived by the owner on Apr 26, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
Process previously failed backfill events in the background #13623
Description
After #13621, we will know if we have previously tried to backfill event and it failed. When we decide to backfill that event again, we should process it in the background so it doesn't block and make /messages slow when we know it will probably fail again.
Follow-up to #13621 and #13622
Part of making /messages faster: #13356
Metadata
Metadata
Assignees
Labels
/messages client API endpoint (`RoomMessageListRestServlet`) (which also triggers /backfill)Performance, both client-facing and admin-facingMost users are unlikely to come across this or unexpected workflowBlocks non-critical functionality, workarounds exist.New features, changes in functionality, improvements in performance, or user-facing enhancements.
Activity
Keep track when we try and fail to process a pulled event (#13589)
Process previously failed backfill events in the background
Process previously failed backfill events in the background (#15585)