This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Long-running /context request on matrix.org after client disconnected
#14443
Labels
A-Context-Endpoint
/context client API endpoint
A-Database
DB stuff like queries, migrations, new/remove columns, indexes, unexpected entries in the db
A-Performance
Performance, both client-facing and admin-facing
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Comments
MadLittleMods
added
A-Performance
|
I think this was fixed by #14461 |
MadLittleMods
added
the
T-Defect
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Follow-up to https://github.com/vector-im/sre-internal/issues/1689 as mentioned by @reivilibre,
There was a
/contextrequest that ran for 12345.92s (3.4 hours) in Matrix HQ (!OGEhHVWSdvArJzumhm:matrix.org) but the client disconnected after 180s (client timeout). This would be a good endpoint candidate to make cancelable (@cancellable).While the
/contextrequest ran, it also degraded database performance for the wholeclient_readerworker so we could limit the exposure by making it cancel on client disconnect. Plus we're doing work for nothing.In the same vein as #14290 for
/searchThe text was updated successfully, but these errors were encountered: