[Systems] [Systems-logs] [Gitorious Processor] fail in PushEventProcessor

[Chris Leonard]

On Tue, Jun 26, 2012 at 4:11 AM, Sascha Silbe <silbe at activitycentral.com> wrote:
> Gitorious <no-reply at git.sugarlabs.org> writes:
>
>> An exception occured in #<PushEventProcessor:0x7f3c392fc570
>>  @action=:update,
> [...]
>>    @git_dir=
>>     "/srv/gitorious/repos/295/815/b0bd4d07242efa579d5d1a570e889aeaf9.git">,
> [...]
>>     "{\"username\":\"pootle\",\"message\":\"f0325a22d687f106e5e1e758b2f4517217e44ccd
>>  ad9045280e8bcc983df6ec2628d5fc922c876975
>>  refs/heads/master\",\"gitdir\":\"295/815/b0bd4d07242efa579d5d1a570e889aeaf9\"}",
> [...]
>> Grit::Git::GitTimeout: Grit::Git::GitTimeout
> [...]
>
> These exceptions are happening rather often and always for Pootle. Can
> we do anything about that?
>
> Pootle commits may be more work for jita than most commits. Maybe just
> increasing the timeout would help? Or is the timeout already so high
> that hitting it is indicative of some deeper issue?

I can tell you that I have been working Pootle pretty hard on a
variety of tasks recently (Honey division, eToys POT refresh, etc.).
I've been performing tasks that will tax it pretty hard, (e.g. running
through a series of reviews/updates from templates/commits) while
having over 100 browser tabs open on it, etc.

Most this is being done in the early hours of the morning US Eastern
time (typically a low usage period) to avoid bogging down the other
uses of the server.  Every once in a rare while I have gotten a server
error in response to a web UI initiated action, but nothing that is
not overcome by waiting and trying it again.

Ultimately, I think the answer will be the migration of Pootle to a VM
on the new hardware that has been acquired.  I have not examined the
specific commit listed to see if it was an event that I triggered.  I
have mostly completed the beating on Pootle I need to do and if there
is a genuine concern that I am causing some sort of harm (as opposed
to just giving the machine a hard workout), I will modify my approach
to future bulk manipulations.

I would suggest waiting to see if this goes away after the Pootle
migration to the new hosting.

Regards,

cjl
Sugar Labs Translation Team Coordinator