[
https://ovirt-jira.atlassian.net/browse/OVIRT-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eyal Edri reassigned OVIRT-2782:
--------------------------------
Assignee: Evgheni Dereveanchin (was: infra)
> Configure Jenkins to wait less and allocate more
> ------------------------------------------------
>
> Key: OVIRT-2782
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2782
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: Daniel Belenky
> Assignee: Evgheni Dereveanchin
>
> By default, Jenkins is configured to wait a few seconds before allocating a
> new node in a hope that a node in use to be freed. We can control this
> setting by setting
> {code:java}
> hudson.slaves.NodeProvisioner.initialDelay=0
> {code}
> We can also control the excessive workload threshold and force Jenkins to
> allocate slaves for jobs in the queue... but, because Jenkins computes the
> excess workload value (which decides if we need to allocate a new node) using
> an EMA, we set it's margins to higher values and it effectively lowers its
> threshold so that Jenkins will allocate nodes faster and in advance.
> The recommended settings by the k8s plugin to spawn a node for every build in
> the queue:
> {code:java}
> -Dhudson.slaves.NodeProvisioner.initialDelay=0
> -Dhudson.slaves.NodeProvisioner.MARGIN=50
> -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85
> {code}
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100108)
_______________________________________________
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/3Y5X2YHBNGV5ZT2UVBEMY3T5APAXNFPB/
