Activity log for bug #506158

Date Who What changed Old value New value Message
2010-01-11 21:50:35 Michael Barnett bug added bug
2010-01-11 21:55:58 Michael Barnett removed subscriber Canonical LOSAs
2010-01-11 21:56:09 Michael Barnett launchpad: status New Invalid
2010-01-11 21:57:41 Michael Barnett launchpad: status Invalid New
2010-01-11 21:59:18 Michael Barnett launchpad: importance Undecided High
2010-01-11 22:09:13 Curtis Hovey affects launchpad malone
2010-01-11 22:09:13 Curtis Hovey malone: status New Triaged
2010-01-11 22:09:29 Curtis Hovey malone: milestone 10.01
2010-01-11 22:26:14 Curtis Hovey malone: assignee Graham Binns (gmb)
2010-01-12 13:24:18 Graham Binns summary checkwatches being abusive towards external sites checkwatches hammers the remote server when asking for changed bugs
2010-01-12 13:26:59 Graham Binns description Checkwatches is hitting external sites too hard (driving apache resource utilization through the roof). What happens: When checkwatches runs it asks the remote server for a list of the bugs that have been updated since a given date (usually the oldest lastchecked date for the current bugwatch set). It does this blindly and doesn't take into account the number of remote bugs its asking about. In the case of gnome-bugs, it was asking about over 13,000 bugs and sending a 52MB POST request to the remote system in order to do so, bringing bugzilla.gnome.org to its knees. What should happen: checkwatches should be aware of the number of remote bugs its asking about and ensure that it's not an unreasonable number (we could use the current batch size as a guideline, for example).
2010-01-12 13:28:20 Graham Binns description What happens: When checkwatches runs it asks the remote server for a list of the bugs that have been updated since a given date (usually the oldest lastchecked date for the current bugwatch set). It does this blindly and doesn't take into account the number of remote bugs its asking about. In the case of gnome-bugs, it was asking about over 13,000 bugs and sending a 52MB POST request to the remote system in order to do so, bringing bugzilla.gnome.org to its knees. What should happen: checkwatches should be aware of the number of remote bugs its asking about and ensure that it's not an unreasonable number (we could use the current batch size as a guideline, for example). What happens: When checkwatches runs it asks the remote server for a list of the bugs that have been updated since a given date (usually the oldest lastchecked date for the current bugwatch set). It does this blindly and doesn't take into account the number of remote bugs its asking about. In the case of gnome-bugs, it was asking about over 13,000 bugs and sending a 52MB POST request to the remote system in order to do so, bringing bugzilla.gnome.org to its knees. See lib/lp/bugs/scripts/checkwatches.py:584 for the offending code What should happen: checkwatches should be aware of the number of remote bugs its asking about and ensure that it's not an unreasonable number (we could use the current batch size as a guideline, for example).
2010-01-12 14:41:03 Graham Binns malone: assignee Graham Binns (gmb)
2010-01-13 11:28:31 Gavin Panella malone: assignee Gavin Panella (allenap)
2010-01-13 17:50:37 Gavin Panella branch linked lp:~allenap/launchpad/stop-checkwatches-hammering-bug-506158
2010-01-13 17:53:01 Gavin Panella malone: status Triaged In Progress
2010-01-14 09:57:07 Gavin Panella branch linked lp:~allenap/launchpad/stop-checkwatches-hammering-bug-506158-devel
2010-01-18 17:38:22 Gavin Panella branch linked lp:~allenap/launchpad/stop-checkwatches-hammering-products-bug-506158
2010-01-20 15:52:51 Gavin Panella malone: status In Progress Fix Committed
2010-01-20 15:58:58 Gavin Panella branch linked lp:~allenap/launchpad/stop-checkwatches-hammering-products-bug-506158-devel
2010-01-20 16:02:15 Martin Mai removed subscriber Martin Mai
2010-01-27 16:26:40 Gavin Panella malone: status Fix Committed Fix Released
2010-02-27 09:59:34 Gavin Panella branch linked lp:~allenap/launchpad/stop-checkwatches-hammering-bug-506158-db-stable