Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-29851

global instance cap not respected for spot instances

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When the build queue piles up new instances are launched. One per waiting job, it seems. I've attached a screenshot of my configuration. The instance cap per AMI doesn't have any effect either.

      I believe this may be related to spot instances not coming up with the Jenkins slave tags, and so not being counted correctly. Though the global cap should apply to the overall number of running instances, no?

        Attachments

          Activity

          Hide
          francisu Francis Upton added a comment -

          s/b resolved in 1.30

          Show
          francisu Francis Upton added a comment - s/b resolved in 1.30
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Francis Upton IV
          Path:
          src/main/java/hudson/plugins/ec2/EC2Cloud.java
          src/main/java/hudson/plugins/ec2/EC2SpotSlave.java
          src/main/java/hudson/plugins/ec2/SlaveTemplate.java
          http://jenkins-ci.org/commit/ec2-plugin/f85b37b8f3ace611191c8b3507d03dcbda999a55
          Log:
          JENKINS-29851 Global instance cap not calculated for spot instances correctly
          JENKINS-32397 Spot instance AMI counting has problems
          JENKINS-32398 Remove spot instance nodes when requests are canceled

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Francis Upton IV Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java src/main/java/hudson/plugins/ec2/EC2SpotSlave.java src/main/java/hudson/plugins/ec2/SlaveTemplate.java http://jenkins-ci.org/commit/ec2-plugin/f85b37b8f3ace611191c8b3507d03dcbda999a55 Log: JENKINS-29851 Global instance cap not calculated for spot instances correctly JENKINS-32397 Spot instance AMI counting has problems JENKINS-32398 Remove spot instance nodes when requests are canceled
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Francis Upton IV
          Path:
          src/main/java/hudson/plugins/ec2/EC2Cloud.java
          http://jenkins-ci.org/commit/ec2-plugin/848fec3b9a473386173a7faabae25ef911d54b36
          Log:
          JENKINS-29851 Global instance cap not calculated for spot instances correctly (fixed NPE)

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Francis Upton IV Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java http://jenkins-ci.org/commit/ec2-plugin/848fec3b9a473386173a7faabae25ef911d54b36 Log: JENKINS-29851 Global instance cap not calculated for spot instances correctly (fixed NPE)
          Hide
          abbm A B added a comment -

          Our instance cap is set to 1, but seems to be completely ignored. Not uncommon for 10 instances to be launched simultaneously. Is there anything required in our EC2 environment / AMI in order for the instance cap to be respected?

          Show
          abbm A B added a comment - Our instance cap is set to 1, but seems to be completely ignored. Not uncommon for 10 instances to be launched simultaneously. Is there anything required in our EC2 environment / AMI in order for the instance cap to be respected?
          Hide
          abbm A B added a comment -

          Our workaround is to manually launch instances before sending the jobs to Jenkins. This is a luxury we have, based on our configuration, that others may not have. But I wanted to share it anyway.

          If the instances are already idle (or in use) then the instance cap is respected and additional slaves are not initiated. It suggests to me that, when inspecting the instance cap, instances that are currently booting up are being ignored.

           

          Show
          abbm A B added a comment - Our workaround is to manually launch instances before sending the jobs to Jenkins. This is a luxury we have, based on our configuration, that others may not have. But I wanted to share it anyway. If the instances are already idle (or in use) then the instance cap is respected and additional slaves are not initiated. It suggests to me that, when inspecting the instance cap, instances that are currently booting up are being ignored.  

            People

            • Assignee:
              francisu Francis Upton
              Reporter:
              arienkock Arien Kock
            • Votes:
              5 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated: