Improve host load balancing on ImportD service

Bug #546029 reported by Stefan Stasik
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad code imports
Triaged
Low
Unassigned

Bug Description

Hello: Currently we have 4 ImportD job servers that process code imports on Launchpad. We use a basic crontab system to launch the processing scripts on a staggered basis (using shell 'sleep') to try to balance how the 4 hosts process the incoming jobs. We need to come up with a improved way of handling these jobs so that the load-balancing happens in a more intelligent way. One of the servers is much more powerful than the others, so a round-robin approach doesn't work well.

Thank you, Stefan Stasik

Revision history for this message
Tom Haddon (mthaddon) wrote :

Does the --max-jobs option do this?

affects: launchpad → launchpad-code
Paul Hummer (rockstar)
Changed in launchpad-code:
status: New → Triaged
importance: Undecided → High
tags: added: code-import
Revision history for this message
Tom Haddon (mthaddon) wrote :

It seems this isn't working as expected. See --max-jobs=3 while galapagos is clearly running 4 jobs.

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote : Re: [Bug 546029] Re: Improve host load balancing on ImportD service

On 27/03/10 01:31, Tom Haddon wrote:
> It seems this isn't working as expected. See --max-jobs=3 while
> galapagos is clearly running 4 jobs.
>
> ** Attachment added: "Screenshot.png"
> http://launchpadlibrarian.net/42049427/Screenshot.png

The second invocation in the cron job still says 4.

I guess we should really kill the need for that hack.

Cheers,
mwh

Revision history for this message
Tom Haddon (mthaddon) wrote :

Ah, thx - now fixed to use --max-jobs=3 on both runs.

Revision history for this message
Steve McInerney (spm) wrote :

we had a funky yesterday, where a single import (afaict - and was the linux kernel) caused sufficient load on galapagos that later importds getting fired off would be sufficiently slowed down that we ended up having a bunch of new importds scheduled from cron all gradually working their way to failing to get a lock and die.

Which also explained the sudden load spike.
https://pastebin.canonical.com/29841/

It did sort itself, but perhaps a light weight wrapper to trap this behaviour may be worthwhile?

Revision history for this message
Tim Penhey (thumper) wrote :

Right now this is a low priority. The high priority bit is to make the git imports much faster. Jelmer has already done much of this and we are testing on staging. We are talking orders of magnitude faster, so that'd be good.

Changed in launchpad-code:
importance: High → Low
Colin Watson (cjwatson)
affects: launchpad → lp-codeimport
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.