supermirror latency monitoring
Bug #44205 reported by
David Allouche
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I updated the bzrk mainline branch on monday, but it took more than 12 hours before being published (that's an unacceptable latency), and the supermirror-pull script did not send any message to the launchpad-errors@ mailing list.
There is not enough information to diagnose latency issues with the branch puller script. It should log to a file (with timestamps) when it starts, which branches it processes (by filesystem id and unique_name) the errors (even non-fatal) it encounters, and when it finishes.
The log files should probably be rotated and deleted after some time to prevent the log data to grow without bound.
To post a comment you must log in.
David, is this still valid?