launchpad-dev team mailing list archive

[Graham Binns <graham@xxxxxxxxxxxxx>]

2010/1/27 Curtis Hovey <curtis.hovey@xxxxxxxxxxxxx>:
> Hi Matt, rocket scientists, et al.
>
> We need to remove the section automatically mark bugs as fix released
> section. I am near tears as remove the feature from the code.
>

Really sorry that we're having to back it out; I know how that must sting.

> I am seeing many timeouts on edge where I saw no timeouts in staging.
> This is very troubling since staging is slower that edge. I tested the
> same projects I tried to create releases for on edge.
>
> The oops on edge indicate that we cannot make mass changes to bugs
> because launchpad cannot build the list subscribers who should be
> notified of the changes. While notify() is sending the signals to
> update bug history, user karma, and bug subscribers, all this work must
> happen in the time of the request.
>
> Launchpad does not have a message queue system, so I would need to
> prepare schema, model, and cron script changes for accommodate this
> feature. All this must happen on staging, so this feature is at least 4
> weeks away. It is probably longer because I worked on this in my after
> hours; this feature is not a goal of the launchpad team.
>
> The problem illustrates that we lack the infrastructure to painlessly
> make an operation asynchronous. By painless, I mean schema and model
> changes take more time to develop than sending a message to some other
> process to do the work. Updating schemas often requires more planning
> code then it took to create them. Moving the the bug notification
> subscribers step to an async proc may help other process too, but the
> bugs team has more important matter work work on.

We do actually have a Jobs system implementation in place for Bugs now
(see lp.bugs.interfaces.bugjob and lp.bugs.interfaces.bugheat), though
I don't know how much use it would be in this instance. Adding new Job
types is a fairly painless procedure, but I guess that in this case
there's still a lot of work that would need to go into moving from our
current system into the new one.

Subscribers have caused us quite a lot of problems for a while, by the
way, so you're not the first person to be knobbled by this kind of
timeout.

-- 
Graham Binns | PGP Key: EC66FA7D