FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Build System

 
 
LinkBack Thread Tools
 
Old 02-26-2010, 02:19 PM
Jeroen van Meeuwen
 
Default buildcapacity - # of builders

On 02/26/2010 04:03 PM, Dennis Gilmore wrote:
> On Friday 26 February 2010 07:03:33 am Jeroen van Meeuwen wrote:
>> On 02/26/2010 01:02 PM, Jeroen van Meeuwen wrote:
>>> On 02/26/2010 12:43 PM, Doug Reiland wrote:
>>>> Does it make any sense of run more one builder on a system or do you
>>>> just control via host.capacity in the database?
>>>
>>> You don't want more then one builder per node. You may want multiple
>>> nodes on one hardware box through virtualization, but each node would
>>> still only have one koji-builder.
>>>
>>> You control the amount of labour the host can/may/will do through
>>> host.capacity in the psql database, as well as the maxjobs setting in
>>> /etc/kojid/kojid.conf (maximum 5 parallel jobs by default).
>>
>> Also note that new tasks won't be taken up by the koji-builder if the
>> load average of the node is 8.00 or greater (I don't recall having
>> modified that setting ever before).
>
> that is not true. the sparc builders have a capacity of 16 and regularly hit
> max capacity. they also regullary have a load of 30-40
>

Right, thanks for the more detailed explanation, I wasn't sure whether I
was doing it right ;-)

As per the explanation, the reason I said 8.00 apparently is related to
the number of CPU cores in the boxes that I use ;-) Again, thanks!

-- Jeroen
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 02-26-2010, 03:13 PM
Mike McLean
 
Default buildcapacity - # of builders

On 02/26/2010 09:58 AM, Mike Bonnet wrote:
> If kojid shuts down cleanly it will free all the tasks it is currently
> working on, to make them available for another builder to process. On
> startup is also frees any tasks it owns before starting to process new
> tasks. In general a kojid restart may result in running tasks being
> started over, but nothing worse than that.

There are a few situations where tasks do not restart cleanly.

newRepo tasks get an error because they fail to recycle their createrepo
subtasks effectively. I've been meaning to fix this but it's generally
not a big issue, kojira will just create a fresh task when it fails.

build tasks can sometimes fail on restart if they've gotten too far
along -- specifically if they've already triggered the build import (the
restart will then fail because the NVR already exists). Of course if it
imported the build then it is mostly done, but the task will show up as
failed (even though the build will show as successful). Also the build
might not be tagged (which can be remedied by simply tagging it manually).

Similarily, a tagBuild task can fail on restart if it got as far as
actually tagging but didn't quite finish. Of course this means the
tagging actually occurred, but the notification will indication
otherwise (or you may see both the success and failure notifications).
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 
Old 02-26-2010, 03:26 PM
Mike McLean
 
Default buildcapacity - # of builders

On 02/26/2010 07:49 AM, Jeroen van Meeuwen wrote:
> waitRepo is a special task; In my experience, if there is no version of
> the repository yet, a task against a build root will automatically have
> a waitRepo task (before even adding the buildArch tasks to the task queue).

waitrepo is used a number of places and can wait for a few different
conditions:
- for specific nvrs to appear (chain-build uses this)
- for a repo newer the a specific timestamp (I don't know if anything
actually uses this right now)
- for any active repo for the tag (the build task uses this when the
repo is not immediately available)


> You can add a waitRepo task to a build task on a per-build basis, either
> through the command-line (koji wait-repo iirc), and possibly as an
> option to the "koji build<options> <tag> (...)" command as well (have
> no experience with such).

The cli wait-repo subcommand doesn't actually create a waitrepo task; it
handles the logic internally.
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys
 

Thread Tools




All times are GMT. The time now is 11:57 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org