Closed Bug 786226 Opened 12 years ago Closed 12 years ago

regularly clean buildbot scheduler database of old schedulers

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 755012

People

(Reporter: bhearsum, Unassigned)

Details

We sometimes hit bugs like 786021 where a really old scheduler gets re-added, and ends up using its really old state from the database, and looking through all changes since then. This can take a very long, and we get nothing scheduled in the meantime.

It would be great to be able to automatically prune old schedulers from the database. I'm not sure if there's enough info in the DB to know which are truly old, though. Maybe any schedulers whose state has a "last_processed" changeid that's N changeids old? (100? 1000?)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.