Skip to content
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.

Sign up for GitHub

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

Jump to bottom

scheduler should property allocate driver-port for etcd-mesos-executor #92

Closed
jdef opened this issue Feb 19, 2016 · 1 comment · Fixed by #93
Closed

scheduler should property allocate driver-port for etcd-mesos-executor #92

jdef opened this issue Feb 19, 2016 · 1 comment · Fixed by #93
Assignees
@jdef
Labels
bug

Comments

@jdef
Copy link
Contributor

jdef commented Feb 19, 2016

... and then the custom executor should bind to that port when setting up the driver instance.
@jdef jdef added the bug label Feb 19, 2016
@jdef
Copy link
Contributor Author

jdef commented Feb 19, 2016

stumbled upon this bug when attempting to reproduce: d2iq-archive/kubernetes-mesos#790

jdef pushed a commit that referenced this issue Feb 20, 2016
fixes #92: properly allocate libprocess port for executor driver; fix…
f877bb3 
… resource allocation to take into account executor resources; executor should attempt to use LIBPROCESS_IP as binding address for compat on multihomed hosts
@jdef jdef mentioned this issue Feb 20, 2016
Merged
@jdef jdef self-assigned this Feb 20, 2016
@jdef jdef added WIP PTAL and removed WIP labels Feb 20, 2016
@jdef jdef closed this as completed in #93 Feb 20, 2016
@jdef jdef removed the PTAL label Feb 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jdef jdef

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

resource allocation-related fixes, etc mesosphere-backup/etcd-mesos
1 participant
@jdef