{"action":"created","issue":{"url":"https://api.github.com/repos/mesosphere/marathon-lb/issues/71","repository_url":"https://api.github.com/repos/mesosphere/marathon-lb","labels_url":"https://api.github.com/repos/mesosphere/marathon-lb/issues/71/labels{/name}","comments_url":"https://api.github.com/repos/mesosphere/marathon-lb/issues/71/comments","events_url":"https://api.github.com/repos/mesosphere/marathon-lb/issues/71/events","html_url":"https://github.com/mesosphere/marathon-lb/issues/71","id":134072034,"number":71,"title":"Stale HAProxy configurations remain listening","user":{"login":"ejether","id":686540,"avatar_url":"https://avatars.githubusercontent.com/u/686540?v=3","gravatar_id":"","url":"https://api.github.com/users/ejether","html_url":"https://github.com/ejether","followers_url":"https://api.github.com/users/ejether/followers","following_url":"https://api.github.com/users/ejether/following{/other_user}","gists_url":"https://api.github.com/users/ejether/gists{/gist_id}","starred_url":"https://api.github.com/users/ejether/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ejether/subscriptions","organizations_url":"https://api.github.com/users/ejether/orgs","repos_url":"https://api.github.com/users/ejether/repos","events_url":"https://api.github.com/users/ejether/events{/privacy}","received_events_url":"https://api.github.com/users/ejether/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2016-02-16T19:17:36Z","updated_at":"2016-02-18T16:46:44Z","closed_at":null,"body":"We are seeing an interesting issue with v1.0.1 of marthon-lb running in SSE.\r\nOn a reconfiguration, occasionally the older process remains listening causing stale configuration and the  newer process to fail.\r\n\r\nI have not be able to reliable reproduce it but it has cause several issues for us recently and the only way. It seems to occur when a service is flapping, or when many deployments are occurring at once. I have a theory that there is a race condition between when the new process has successfully started and the pidfile is read by the next starting process. (https://github.com/mesosphere/marathon-lb/blob/master/service/haproxy/run#L30)\r\n\r\nI'm interested in any ideas anyone might have on how to reliably reproduce this or how to guaranty it doesn't bite us anymore. We are not ready to upgrade to v1.1.0 because we don't currently have an up front list of ports."},"comment":{"url":"https://api.github.com/repos/mesosphere/marathon-lb/issues/comments/185809479","html_url":"https://github.com/mesosphere/marathon-lb/issues/71#issuecomment-185809479","issue_url":"https://api.github.com/repos/mesosphere/marathon-lb/issues/71","id":185809479,"user":{"login":"ejether","id":686540,"avatar_url":"https://avatars.githubusercontent.com/u/686540?v=3","gravatar_id":"","url":"https://api.github.com/users/ejether","html_url":"https://github.com/ejether","followers_url":"https://api.github.com/users/ejether/followers","following_url":"https://api.github.com/users/ejether/following{/other_user}","gists_url":"https://api.github.com/users/ejether/gists{/gist_id}","starred_url":"https://api.github.com/users/ejether/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ejether/subscriptions","organizations_url":"https://api.github.com/users/ejether/orgs","repos_url":"https://api.github.com/users/ejether/repos","events_url":"https://api.github.com/users/ejether/events{/privacy}","received_events_url":"https://api.github.com/users/ejether/received_events","type":"User","site_admin":false},"created_at":"2016-02-18T16:46:44Z","updated_at":"2016-02-18T16:46:44Z","body":"Ok, I was under the impression (only because I didn't investigate too deeply) that it wouldn't work if I didn't have all the $PORTS configured. That makes it a lot easier to test. Thanks"}}