![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Francis Upton
|
|
Components:
|
ec2, plugin |
|
Created:
|
19/Feb/13 10:02 PM
|
|
Description:
|
As soon as I queue a single build, the ec2 plugin spins up multiple ec2 build slaves at the same instant. My logs show:
Feb 19, 2013 12:58:03 PM hudson.slaves.NodeProvisioner update
INFO: www.edbookfest dev-server build slave (ami-089c957c) provisioning successfully completed. We have now 2 computer(s)
Feb 19, 2013 12:57:54 PM hudson.slaves.NodeProvisioner update
INFO: www.edbookfest dev-server build slave (ami-089c957c) provisioning successfully completed. We have now 2 computer(s)
Feb 19, 2013 12:56:10 PM hudson.slaves.NodeProvisioner update
INFO: Started provisioning www.edbookfest dev-server build slave (ami-089c957c) from ec2-eu-west-1 with 2 executors. Remaining excess workload:-3.0
Feb 19, 2013 12:56:10 PM hudson.slaves.NodeProvisioner update
INFO: Started provisioning www.edbookfest dev-server build slave (ami-089c957c) from ec2-eu-west-1 with 2 executors. Remaining excess workload:-1.0
Feb 19, 2013 12:56:09 PM hudson.slaves.NodeProvisioner
FINE: Excess workload 1.0 detected. (planned capacity=5.6E-45,Qlen=8.921825E-28,idle=2.4934977E-16&0,total=0m,=1.0)
I think it only stops at two because of the instance cap, I have experienced it putting in more. I tried increasing the number of executors per instance to two in the hope that would make it realise it had capacity coming onstream but that hasn't made any difference, as you see above it goes immediately to -3.0 excess workload.
I think this may be related to JENKINS-5334 and JENKINS-6691 but they seem both to involve slightly different circumstances either where additional builders are correctly required, or where there is a time delay in start up.
|
|
Environment:
|
Jenkins 1.499, Amazon EC2 plugin v1.17
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Andrew Coulton
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
