jubany package importer stopped?

[Jonathan Lange]

On 16 April 2012 20:56, Max Bowsher <_ at maxb.eu> wrote:
> On 16/04/12 13:38, John Arbash Meinel wrote:
>> On 4/16/2012 7:40 AM, Stephanie Miller wrote:
>>> Hi folks,
>>
>>> Our monitoring system is currently showing an alert for jubany's
>>> package importer process, saying that no python processes were
>>> found. Restarting mass-import doesn't seem to resolve the alert.
>>> Additionally /srv/package-import.canonical.com/new/logs/debug_log
>>> has lots of messages about the database being locked.
>>
>>> Is this the current expected state? If not, what action should I
>>> take, if any?
>>
>>> Thanks, Stephane (Canonical IS)
>>
>>
>> I don't believe this is the expected state. In chatting with Max B and
>> Vincent, it looks like it is related to some of the changes that James
>> Westby did recently (introducing Storm for the database layer.)
>>
>> James is in Canadian TZ now, so I'll try to get ahold of him this
>> afternoon.
>
>
> I've just "kill -9"-ed the stuck mass-import python process and
> restarted it, requeuing the spuriously failed jobs, so that the backlog
> can be worked on.
>
> This is only going to happen again, though, unless we:
>
>  a) find where mass-import is holding its db open infinitely
>
> OR
>
>  b) revert the storm integration
>
> I feel we should revert the storm integration until it is more mature,
> unless James can fix it very soon, given it's breaking UDD, and was only
> added for other re-users of parts of the code.
>

I'd only be OK with this if we can figure out some way of making it
more mature. We're going to be using it with postgresql, so this isn't
going to be an issue for us.

jml