-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to get mesos-plugin built against mesos 0.14.0 from mesosphere #1
Comments
Hmm. That is surprising. It might be that the jar supplied by Mesossphere is not built from the correct sha. You could ask them to build the jar from mesos-0.14.0-rc5 tag or wait for the official 0.14.0 release which includes publishing the jar to Apache Maven repo. |
I published the proper 0.14.0 jar to the staging repository at https://repository.apache.org/content/repositories/orgapachemesos-148. Update your pom to point to this repo and do a "mvn clean package". Let me know if it works. |
By switching to the repository you suggested and changing to mesos version 0.14.0-rc5 in the pom I was able to generate a clean build of mesos-plugin. However configuring the plugin in jenkins does not seem to be working for me. I am running jenkins 1.534 and when creating a cloud I'm pointing to my native mesos library on the server running jenkins at
I see the same results when testing from a local jenkins instance brought up with |
That seems to be a bug in how test connection! Thanks for the report. Committed a fix. Let me know if you are still having problems. |
This fixed my connection issue thank you. Closing. |
Updated mesos dependency to 0.18.1.
The current synchronized on MesosImpl method are pointless since what we are looking for is to lock access to JenkinsScheduler. thread-deadlock : [Computer.threadPoolForRemoting [jenkinsci#4] locked on java.util.concurrent.locks.ReentrantLock$NonfairSync@7991f96c (owned by jenkins.util.Timer [jenkinsci#5]): at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199) at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209) at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:187) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:58) at hudson.slaves.NodeProvisioner$1.run(NodeProvisioner.java:173) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) , Computer.threadPoolForRemoting [jenkinsci#1] locked on java.util.concurrent.locks.ReentrantLock$NonfairSync@55469258 (owned by jenkins.util.Timer [jenkinsci#5]): at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199) at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209) at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285) at org.jenkinsci.plugins.mesos.JenkinsScheduler.supervise(JenkinsScheduler.java:848) at org.jenkinsci.plugins.mesos.JenkinsScheduler.terminateJenkinsSlave(JenkinsScheduler.java:254) at org.jenkinsci.plugins.mesos.MesosImpl.stopJenkinsSlave(MesosImpl.java:36) at org.jenkinsci.plugins.mesos.MesosComputerLauncher.terminate(MesosComputerLauncher.java:122) at org.jenkinsci.plugins.mesos.MesosSlave.terminate(MesosSlave.java:92) at org.jenkinsci.plugins.mesos.MesosComputerLauncher.launch(MesosComputerLauncher.java:68) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:238) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) , jenkins.util.Timer [jenkinsci#5] locked on org.jenkinsci.plugins.mesos.MesosImpl@5e9486e (owned by Computer.threadPoolForRemoting [jenkinsci#1]): at org.jenkinsci.plugins.mesos.MesosImpl.isSchedulerRunning(MesosImpl.java:15) at org.jenkinsci.plugins.mesos.MesosCloud.provision(MesosCloud.java:306) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:701) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:305) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:58) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:796) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
We are running the mesosphere.io debian package of mesos 0.14.0 in our cluster and I was trying to get mesos-plugin to build against this version on my mac. I added the following to the pom.xml in order to access the mesos 0.14.0 jar file from the mesosphere maven repo:
My dependencies have also been updated accordingly to grab 0.14.0:
This is the stack trace I get when running mvn package with this configuration:
I'm assuming at this point that the code is not compatible with 0.14.0?
The text was updated successfully, but these errors were encountered: