I tried to minimize the number of executors on master and try to run the job, But no luck. Changed EC2 instance size to little bit low and increased number of executors(in order increase more load the slave). Job waited for couple of minutes(~5 minutes) and started another slave.
*Solution*: Your cluster should be overloaded for more than couple of minutes to add a new dynamic slave. On Friday, August 5, 2016 at 10:39:07 AM UTC-7, praveen wrote: > > *Goal:* I would like to use Amazon Ec2 Plugin > <https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin> to add > dynamic slaves to Jenkins based on the load. > > > *Architecture:* Jenkins Master + 4 slaves + dynamic slaves (based on the > requirement) > 1st job runs on dynamic slave (no concurrent builds) - label1 (ami-12345) > 2nd job runs concurrently on dynamic slaves - label2 (ami-23314) > > These two has different AMI and different labels. > > > *PROBLEM:* first job is able to spin up the instance and executes job > everything looks good. If I run the 2nd job Jenkins able to spin up the > instance, However if jobs are queued up it's not adding new slaves.Even > though I added the instance to 4 for that AMI(cloud instance cap 10). > > > Can somebody help me on this? > > > Jenkins v1.656 > Amazon EC2 plugin v1.31 > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/47d6c6cc-33d5-4dbb-8104-382fc804e5ab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
