{"action":"created","issue":{"url":"https://api.github.com/repos/jenkinsci/mesos-plugin/issues/83","labels_url":"https://api.github.com/repos/jenkinsci/mesos-plugin/issues/83/labels{/name}","comments_url":"https://api.github.com/repos/jenkinsci/mesos-plugin/issues/83/comments","events_url":"https://api.github.com/repos/jenkinsci/mesos-plugin/issues/83/events","html_url":"https://github.com/jenkinsci/mesos-plugin/issues/83","id":56037835,"number":83,"title":"Jenkins slave never successfully connects to the Jenkins master","user":{"login":"barkerd427","id":6106821,"avatar_url":"https://avatars.githubusercontent.com/u/6106821?v=3","gravatar_id":"","url":"https://api.github.com/users/barkerd427","html_url":"https://github.com/barkerd427","followers_url":"https://api.github.com/users/barkerd427/followers","following_url":"https://api.github.com/users/barkerd427/following{/other_user}","gists_url":"https://api.github.com/users/barkerd427/gists{/gist_id}","starred_url":"https://api.github.com/users/barkerd427/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/barkerd427/subscriptions","organizations_url":"https://api.github.com/users/barkerd427/orgs","repos_url":"https://api.github.com/users/barkerd427/repos","events_url":"https://api.github.com/users/barkerd427/events{/privacy}","received_events_url":"https://api.github.com/users/barkerd427/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-01-30T14:14:16Z","updated_at":"2015-04-09T19:06:46Z","closed_at":"2015-03-06T15:37:56Z","body":"At least once a day, a Jenkins slave never actually registers with the master. It has downloaded the appropriate jar, but it is then unable to connect to the master. There should be some method of cleaning up orphaned slaves that are unable to connect. I'm not sure if it's as simple as updating the slave jar to kill itself after a certain amount of time given the right argument, or if it is better to include some management system in this plugin."},"comment":{"url":"https://api.github.com/repos/jenkinsci/mesos-plugin/issues/comments/91329898","html_url":"https://github.com/jenkinsci/mesos-plugin/issues/83#issuecomment-91329898","issue_url":"https://api.github.com/repos/jenkinsci/mesos-plugin/issues/83","id":91329898,"user":{"login":"maselvaraj","id":6958022,"avatar_url":"https://avatars.githubusercontent.com/u/6958022?v=3","gravatar_id":"","url":"https://api.github.com/users/maselvaraj","html_url":"https://github.com/maselvaraj","followers_url":"https://api.github.com/users/maselvaraj/followers","following_url":"https://api.github.com/users/maselvaraj/following{/other_user}","gists_url":"https://api.github.com/users/maselvaraj/gists{/gist_id}","starred_url":"https://api.github.com/users/maselvaraj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/maselvaraj/subscriptions","organizations_url":"https://api.github.com/users/maselvaraj/orgs","repos_url":"https://api.github.com/users/maselvaraj/repos","events_url":"https://api.github.com/users/maselvaraj/events{/privacy}","received_events_url":"https://api.github.com/users/maselvaraj/received_events","type":"User","site_admin":false},"created_at":"2015-04-09T19:06:46Z","updated_at":"2015-04-09T19:06:46Z","body":"@barkerd427 By any chance was your Jenkins hogging the resource offers sent by Mesos when you had this issue? I had a strange issue in my cluster where one Jenkins swallowing all the resources leaving others starving. Looking into the logs, in one of the tasks I saw \r\n\"INFO: Restarting slave via jenkins.slaves.restarter.UnixSlaveRestarter...\""}}