Write a script to spread out clumps of bug watches

Bug #386421 reported by Graham Binns
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Bug 364450 occurs when there are too many bug watches to be updated at one time. This causes certain parts of checkwatches' operations to take too long, causing a TooMuchTimeSkew error to be raised, even if there isn't actually a time skew.

Whilst checkwatches should deal with these situations better, we can mitigate matters by writing a script that will take all the bug watches for a bug tracker and spread their lastchecked times out evenly throughout the day. This will have the effect of reducing the number of watches checked at any one time to a sensible level. This script could be re-run at any point if this problem recurs, say after a large import of bugs from an external tracker.

Revision history for this message
Graham Binns (gmb) wrote :

Unmilestoning this. The original problem has been resolved so, whilst this would be useful it's not urgent right now.

Changed in malone:
milestone: 2.2.6 → none
status: In Progress → Triaged
Revision history for this message
Graham Binns (gmb) wrote :

Marking this as low. The recent multithreaded checkwatches work should further reduce the need for this.

Changed in malone:
assignee: Graham Binns (gmb) → nobody
importance: Medium → Low
Revision history for this message
Gavin Panella (allenap) wrote :

The fix for bug 506158 may make this unnecessary.

tags: added: story-reliable-bug-syncing
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.