Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Keep track when we try to backfill an event #13621

Closed
@MadLittleMods

Description

@MadLittleMods

Mentioned in internal doc about speeding up /messages. Related to #13356


Keep track when we try to backfill an event. In other words, when an event fails to backfill, we can record it in the database.

This is a building block so we can later:

  1. Only try to backfill from an event if we haven't tried recently -> Only try to backfill event if we haven't tried before recently #13622
  2. When we decide to backfill that event again, process it in the background so it doesn't block and make /messages slow when we know it will probably fail again -> Process previously failed backfill events in the background #13623

Metadata

Metadata

Assignees

Labels

A-Messages-Endpoint/messages client API endpoint (`RoomMessageListRestServlet`) (which also triggers /backfill)A-PerformancePerformance, both client-facing and admin-facingO-UncommonMost users are unlikely to come across this or unexpected workflowS-MinorBlocks non-critical functionality, workarounds exist.T-TaskRefactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions