Closed Bug 1497108 Opened 6 years ago Closed 5 years ago

Limit history results to avoid very long running queries

Categories

(Release Engineering Graveyard :: Applications: Balrog (backend), enhancement, P3)

Product:
Release Engineering Graveyard
Component:
Applications: Balrog (backend)
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED MOVED

People

(Reporter: nthomas, Unassigned)

Details

Some of the history tables are very large despite our cleanup procedures, for example Firefox-mozilla-central-nightly-latest turns over. An unbounded or not-very-bounded query on the history UI [1] or API can mean the admin host is unresponsive while it tries to deal with all the data it's getting from the DB. Meanwhile nginx has already given up and returned a 502 to the client, which might rerun the query! We should check if we have limits in place so that we don't overwhelm the server. [1] https://aus4-admin.mozilla.org/change_logs
Priority: -- → P3

Moved to https://github.com/mozilla-releng/balrog/issues/1101

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → MOVED
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.