[JIRA] [ec2-plugin] (JENKINS-32915) Spot instance launched one after another until capacity reached for single task in queue
Title: Message Title Francis Upton closed an issue as Fixed 1.32 Jenkins / JENKINS-32915 Spot instance launched one after another until capacity reached for single task in queue Change By: Francis Upton Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32915) Spot instance launched one after another until capacity reached for single task in queue
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32915 Re: Spot instance launched one after another until capacity reached for single task in queue Code changed in jenkins User: James Judd Path: src/main/java/hudson/plugins/ec2/EC2AbstractSlave.java src/main/java/hudson/plugins/ec2/EC2Cloud.java http://jenkins-ci.org/commit/ec2-plugin/ac5574e23654ae1a7cff8be6bced44b3d6320470 Log: JENKINS-32915 (#193) JENKINS-32915: Corrected horizontal scaling if cloud/job label is null - is not defined in configuration. Better handling of inproper Jenkins core manegment over excessWorkload - if an instance takes 5 minutes to wake up Jenkins does not take it into consideration and tries to provision more until capacity is reached or queue is picked finally. Added logging message that provisioning for spot instance will not be possible if label is not configured. It should be made explicit for the user in configuration that it is needed. JENKINS-32915: Added missing implementation of method JENKINS-32915: Amendments to match tested bottom up code to minimize risk of inproper behaviour. JENKINS-32915: Negation fix JENKINS-32915: Refactored code to make it more readable and perform better JENKINS-32915: Refactored code to scale out properly. Added warning messages, information messages, amended future task to hold for timeout time Cleaning up PR as requested by @francisu Add Comment
[JIRA] [ec2-plugin] (JENKINS-32915) Spot instance launched one after another until capacity reached for single task in queue
Title: Message Title Mateusz Zając commented on JENKINS-32915 Re: Spot instance launched one after another until capacity reached for single task in queue Pull request created. https://github.com/jenkinsci/ec2-plugin/pull/186 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32915) Spot instance launched one after another until capacity reached for single task in queue
Title: Message Title Mateusz Zając assigned an issue to Mateusz Zając Jenkins / JENKINS-32915 Spot instance launched one after another until capacity reached for single task in queue Change By: Mateusz Zając Assignee: Francis Upton Mateusz Zając Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32915) Spot instance launched one after another until capacity reached for single task in queue
Title: Message Title Mateusz Zając started work on JENKINS-32915 Change By: Mateusz Zając Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32915) Spot instance launched one after another until capacity reached for single task in queue
Title: Message Title Mateusz Zając commented on JENKINS-32915 Re: Spot instance launched one after another until capacity reached for single task in queue I addressed the issue here: https://github.com/jenkinsci/ec2-plugin/compare/master...zajacmp3:JENKINS-32915?expand=1 I will be soon creating a PR after writing unit tests. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32915) Spot instance launched one after another until capacity reached for single task in queue
Title: Message Title
Mateusz Zając updated an issue
Jenkins / JENKINS-32915
Spot instance launched one after another until capacity reached for single task in queue
Change By:
Mateusz Zając
For single element in queue with not slaves attached and master executors set to 0 plugin as designed starts launching spot instances. It does not stop physically until capacity is reached. It still tries until task from queue is picked up by worker that launches after ~3mlogs ALL:{code:java}Feb 12, 2016 12:17:38 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotLaunching ami-6c645106 for template Jenkins Build AgentFeb 12, 2016 12:17:39 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotSpot instance id in provision: sir-02g4tk2dFeb 12, 2016 12:17:39 PM INFO hudson.plugins.ec2.EC2Cloud provisionAttempting provision - finished, excess workload: 0Feb 12, 2016 12:17:39 PM INFO hudson.slaves.NodeProvisioner$StandardStrategyImpl applyStarted provisioning Jenkins Build Agent (ami-6c645106) from ec2-Amazon profile with 1 executors. Remaining excess workload: -0.282Feb 12, 2016 12:17:39 PM INFO hudson.plugins.ec2.EC2Cloud$1 callExpected - Spot instance null failed to connect on initial provisionFeb 12, 2016 12:17:47 PM INFO hudson.slaves.NodeProvisioner$2 runJenkins Build Agent (ami-6c645106) provisioning successfully completed. We have now 3 computer(s)Feb 12, 2016 12:17:48 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotLaunching ami-6c645106 for template Jenkins Build AgentFeb 12, 2016 12:17:49 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotSpot instance id in provision: sir-02g3vkvjFeb 12, 2016 12:17:49 PM INFO hudson.plugins.ec2.EC2Cloud provisionAttempting provision - finished, excess workload: 0Feb 12, 2016 12:17:49 PM INFO hudson.slaves.NodeProvisioner$StandardStrategyImpl applyStarted provisioning Jenkins Build Agent (ami-6c645106) from ec2-Amazon profile with 1 executors. Remaining excess workload: -0.254Feb 12, 2016 12:17:49 PM INFO hudson.plugins.ec2.EC2Cloud$1 callExpected - Spot instance null failed to connect on initial provisionFeb 12, 2016 12:17:57 PM INFO hudson.slaves.NodeProvisioner$2 runJenkins Build Agent (ami-6c645106) provisioning successfully completed. We have now 4 computer(s)Feb 12, 2016 12:17:58 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotLaunching ami-6c645106 for template Jenkins Build AgentFeb 12, 2016 12:17:59 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotSpot instance id in provision: sir-02g254a9Feb 12, 2016 12:17:59 PM INFO hudson.plugins.ec2.EC2Cloud provisionAttempting provision - finished, excess workload: 0Feb 12, 2016 12:17:59 PM INFO hudson.slaves.NodeProvisioner$StandardStrategyImpl applyStarted provisioning Jenkins Build Agent (ami-6c645106) from ec2-Amazon profile with 1 executors. Remaining excess workload: -0.229Feb 12, 2016 12:17:59 PM INFO hudson.plugins.ec2.EC2Cloud$1 callExpected - Spot instance null failed to connect on initial provisionFeb 12, 2016 12:18:07 PM INFO hudson.slaves.NodeProvisioner$2 runJenkins Build Agent (ami-6c645106) provisioning successfully completed. We have now 5 computer(s)Feb 12, 2016 12:18:08 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotLaunching ami-6c645106 for template Jenkins Build AgentFeb 12, 2016 12:18:09 PM INFO
[JIRA] [ec2-plugin] (JENKINS-32915) Spot instance launched one after another until capacity reached for single task in queue
Title: Message Title Mateusz Zając created an issue Jenkins / JENKINS-32915 Spot instance launched one after another until capacity reached for single task in queue Issue Type: Bug Assignee: Francis Upton Attachments: Capture.PNG, Capture2.PNG Components: ec2-plugin Created: 12/Feb/16 12:53 PM Environment: Jenkins ver. 1.647 java7 slaves java8 from oracle EC2 plugin 1.31 Launched in VPC in AWS along with Slaves. Open ports 443, 22, 9090 (for slave communication) communication in VPC allowed only using private ip addresses. Labels: ec2-plugin plugin spot Priority: Minor Reporter: Mateusz Zając For single element in queue with not slaves attached and master executors set to 0 plugin as designed starts launching spot instances. It
