Dataflow job id: 2016-01-13_16_00_09-15016519893798477319
Pipeline was configured with the following worker/scaling config:
min 2 workers
max 50 workers
However, the job scaled to 55 workers. Why was the max worker value of 50 not honoured?
Jan 14, 2016, 11:00:10 AM
(77f7e53b4884ba02): Autoscaling: Enabled for job 2016-01-13_16_00_09-15016519893798477319 between 1 and 1000000 worker processes.
Jan 14, 2016, 11:00:17 AM
(374d4f69f65e2506): Worker configuration: n1-standard-1 in us-central1-a.
Jan 14, 2016, 11:00:18 AM
(28acda8454e90ad2): Starting 2 workers...
Jan 14, 2016, 11:01:49 AM
(cf611e5d4ce4784d): Autoscaling: Resizing worker pool from 2 to 50.
Jan 14, 2016, 11:06:20 AM
(36c68efd7f1743cf): Autoscaling: Resizing worker pool from 50 to 55.
This turned out to be a bug in our code. We were calling the wrong method. We need to call setMaxNumWorkers, and not setNumWorkers.
Related
I had scheduled pulling in Jenkins every 5 minutes: */5 * * * *.
I committed changes to SVN, I can see them in SVN history (logs).
Jenkins starting the build, but it shows: Revision: x
No changes. And everything what was configured is running.
After 5 minutes Jenkins starts another run, with message: Revision: x+1
Changes
just for test Jenkins deploy (detail)
by UserName
After, for test purposes I have changed to * * * * * to run every minute, and the results were such:
Jenkins runs:
Success > Console Output#176 Nov 29, 2018 2:14 PM
Success > Console Output#175 Nov 29, 2018 2:13 PM
Success > Console Output#174 Nov 29, 2018 2:11 PM
Success > Console Output#173 Nov 29, 2018 2:10 PM
Success > Console Output#172 Nov 29, 2018 2:09 PM
Success > Console Output#171 Nov 29, 2018 2:08 PM
Success > Console Output#170 Nov 29, 2018 2:07 PM
Success > Console Output#169 Nov 29, 2018 2:06 PM
---Commit goes here
Success > Console Output#168 Nov 29, 2018 1:01 PM
from 2.06 he see that there is changes, he run job, but it really didn't see what changes was there, and only at 2:14 it wrote SVN commit message.
also in Recent Changes logs:
Changes
176 (Nov 29, 2018 2:14:19 PM)
just for test Jenkins deploy — UserName / detail
168 (Nov 29, 2018 1:01:36 PM)
It is strange behavior, could someone have idea, where could be the issue?
Based on the conversation, We have found out the culprit was the Time Difference of the 2 servers(Jenkins and SVN) approx 7-8 mins was the issue.
Why does this happen ?
Jenkins realized that a new version was available, but couldn't check it out
as long as its own time was smaller than the new versions time.
A similar issue is described here:
Why up-to-date files committed to SVN will not be immediately pulled out by Hudson to build
I am having trouble understanding the error in the project
Although my build steps pass
02:40:40 api_1 | complete: 6 passing, 0 failing, 0 errors, 0 skipped, 6 total
It is failing. This is output from jenkins log
[root#ip-10-14-6-40 jenkins]# tail jenkins.log
Nov 14, 2018 2:40:35 AM hudson.model.AsyncPeriodicWork$1 run
INFO: Finished DockerContainerWatchdog Asynchronous Periodic Work. 11 ms
Nov 14, 2018 2:40:36 AM jenkins.plugins.slack.StandardSlackService publish
INFO: Posting succeeded
Nov 14, 2018 2:40:46 AM jenkins.plugins.slack.StandardSlackService publish
INFO: Posting succeeded
Nov 14, 2018 2:40:46 AM org.jenkinsci.plugins.workflow.job.WorkflowRun
finish
INFO: tal-ci-test/spec #101 completed: FAILURE
Nov 14, 2018 2:40:46 AM
org.terracotta.jenkins.plugins.postcompleted.PostCompletedRunListener
onCompleted
INFO: The url to submit to is not valid, please check your global
configuration
I need to schedule a jenkins job to run every 90 minutes
I tried the following but it did not work
*/45 */1 * * *
But the job ran ever hour and then at every 45 minutes like
Sep 15, 2016 1:46:09 AM
Sep 15, 2016 1:01:09 AM
Sep 15, 2016 12:46:09 AM
Sep 15, 2016 12:01:09 AM
Sep 14, 2016 11:46:09 PM
Sep 14,2016 11:01:09 PM
and so on
Can any one please suggest me how this is done
You may have to specify two cron jobs for it in the scheduler like this in the same jenkins job - very similar to what one would do for a normal cron in Linux
0 0,3,6,9,12,15,18,21 * * * /path/to/script
45 1,4,7,10,13,16,19,22 * * * /path/to/script
I'm not sure how to go about debugging this issue. Jenkins on restarts takes forever and from the logs I can see that its sitting trying to launch the slave
06/25/15 14:03:34] SSH Launch of Slave1 on dom-jenkins-sl1.cloud.dev.phx3.gdg failed in 179,907 ms
Jun 25, 2015 2:05:06 PM hudson.slaves.SlaveComputer tryReconnect
INFO: Attempting to reconnect Slave1
Jun 25, 2015 2:05:07 PM org.jenkinsci.main.modules.sshd.SSHD start
INFO: Started SSHD at port 33090
Jun 25, 2015 2:05:07 PM jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
Jun 25, 2015 2:05:07 PM org.jenkinsci.plugins.skipcert.ItemListenerImpl onLoaded
INFO: Bypassing certificate check
Jun 25, 2015 2:05:08 PM hudson.WebAppMain$3 run
INFO: Jenkins is fully up and running
[06/25/15 14:05:08] SSH Launch of Slave1 on dom-jenkins-sl1.cloud.dev.phx3.gdg completed in 1,923 ms
And yet on the second try 2 minutes later it works just fine. Any ideas?
I'm using the jenkins mesos plugin for CI.
Initially, I followed the following tutorial: http://www.ebaytechblog.com/2014/05/12/delivering-ebays-ci-solution-with-apache-mesos-part-ii/
but the jenkins itself was not being setup via this. (I got error could not load config.xml file, even there was one)
Then I followed https://rogerignazio.com/blog/scaling-jenkins-mesos-marathon/
, and I was able to run jenkins master (jenkin framework/scheduler), but when I define the scripts to run, the jenkins-slaves are not being created. I think I'm missing some configuration regarding slaves. Can you tell me, what's the reason that the slaves are not being created to run jobs.
On the jenkins build page, I'm getting :
(pending—Waiting for next available executor)
And in the jenkins-logs, i'm getting following error:
INFO: Provisioning Jenkins Slave on Mesos with 1 executors. Remaining excess workload: 0 executors)
Jun 19, 2015 4:02:55 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply
INFO: Started provisioning MesosCloud from MesosCloud with 1 executors. Remaining excess workload: 0
Jun 19, 2015 4:02:55 PM org.jenkinsci.plugins.mesos.MesosComputerLauncher <init>
INFO: Constructing MesosComputerLauncher
Jun 19, 2015 4:02:55 PM org.jenkinsci.plugins.mesos.MesosSlave <init>
INFO: Constructing Mesos slave mesos-jenkins-1f8691df-9918-4175-87b3-bcc3de80b258 from cloud
Jun 19, 2015 4:03:05 PM org.jenkinsci.plugins.mesos.MesosComputerLauncher launch
INFO: Launching slave computer mesos-jenkins-1f8691df-9918-4175-87b3-bcc3de80b258
Jun 19, 2015 4:03:05 PM org.jenkinsci.plugins.mesos.MesosComputerLauncher launch
INFO: Sending a request to start jenkins slave mesos-jenkins-1f8691df-9918-4175-87b3-bcc3de80b258
Jun 19, 2015 4:03:05 PM org.jenkinsci.plugins.mesos.JenkinsScheduler requestJenkinsSlave
INFO: Enqueuing jenkins slave request
Jun 19, 2015 4:03:05 PM hudson.slaves.NodeProvisioner update
INFO: MesosCloud provisioning successfully completed. We have now 2 computer(s)
java.lang.NullPointerException
at org.jenkinsci.plugins.mesos.JenkinsScheduler.matches(JenkinsScheduler.java:306)
at org.jenkinsci.plugins.mesos.JenkinsScheduler.resourceOffers(JenkinsScheduler.java:252)
Jun 19, 2015 4:03:06 PM org.jenkinsci.plugins.mesos.JenkinsScheduler$1 run
SEVERE: The Mesos driver was aborted! Status code: 3
Edit: I think I'm getting error, because I've not defined any container port mappings.
Can anyone tell me how to do so?
Update : Actually there were many problems with 0.7 version of mesos plugin. So, I simply downgraded to 0.6 version.
For port mappings on marathon have a look here.
Hope this helps!