![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Vinod Kone
|
|
Components:
|
mesos-plugin |
|
Created:
|
26/Jan/15 2:35 PM
|
|
Description:
|
When using the Jenkins Mesos plugin the Scheduler ends up in a state where it keeps spinning up / tearing down agents without actually performing any builds.
The following block is repeatedly logged (with new machine IDs each time):
Jan 26, 2015 2:22:56 PM INFO org.jenkinsci.plugins.mesos.MesosSlave
Constructing Mesos slave
Jan 26, 2015 2:22:59 PM INFO org.jenkinsci.plugins.mesos.JenkinsScheduler resourceOffers
Received offers 1
Jan 26, 2015 2:23:03 PM INFO org.jenkinsci.plugins.mesos.MesosComputerLauncher launch
Launching slave computer mesos-jenkins-21864fdb-738e-4d74-a395-a51c3821958f
Jan 26, 2015 2:23:03 PM WARNING org.jenkinsci.plugins.mesos.MesosComputerLauncher launch
Not launching mesos-jenkins-21864fdb-738e-4d74-a395-a51c3821958f because the Mesos Jenkins scheduler is not running
Jan 26, 2015 2:23:03 PM INFO org.jenkinsci.plugins.mesos.MesosSlave terminate
Terminating slave mesos-jenkins-21864fdb-738e-4d74-a395-a51c3821958f
Jan 26, 2015 2:23:03 PM INFO hudson.slaves.NodeProvisioner update
MesosCloud provisioning successfully completed. We have now 2 computer(s)
Jan 26, 2015 2:23:03 PM INFO org.jenkinsci.plugins.mesos.MesosCloud provision
Provisioning Jenkins Slave on Mesos with 1 executors. Remaining excess workload: 0 executors)
Jan 26, 2015 2:23:03 PM INFO hudson.slaves.NodeProvisioner$StandardStrategyImpl apply
Started provisioning MesosCloud from MesosCloud with 1 executors. Remaining excess workload: 0
Jan 26, 2015 2:23:03 PM INFO org.jenkinsci.plugins.mesos.MesosComputerLauncher
Constructing MesosComputerLauncher
Jan 26, 2015 2:23:04 PM INFO org.jenkinsci.plugins.mesos.JenkinsScheduler terminateJenkinsSlave
Terminating jenkins slave mesos-jenkins-21864fdb-738e-4d74-a395-a51c3821958f
Jan 26, 2015 2:23:04 PM WARNING org.jenkinsci.plugins.mesos.JenkinsScheduler terminateJenkinsSlave
Asked to kill unknown mesos task value: "mesos-jenkins-21864fdb-738e-4d74-a395-a51c3821958f"
The framework state in mesos reports the following:
Name: Jenkins Scheduler
Active Tasks: 1
CPUs: 5.55111512312578e-17
Mem: 0 B
Max Share: 2.77555756156289e-15%
This happens infrequently, but can be occur more than once a day when under heavy load.
|
|
Project:
|
Jenkins
|
|
Labels:
|
plugin
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Andrew Slater
|
|
|
|
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/d/optout.
