You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2013/04/10 00:22:16 UTC
[jira] [Created] (MESOS-431) Port isolation / sharing in the
ephemeral range.
Benjamin Mahler created MESOS-431:
-------------------------------------
Summary: Port isolation / sharing in the ephemeral range.
Key: MESOS-431
URL: https://issues.apache.org/jira/browse/MESOS-431
Project: Mesos
Issue Type: Brainstorming
Reporter: Benjamin Mahler
We currently have yet to enforce the port allocations: MESOS-359
An additional issue is that we don't enforce any kind of fairness in the ephemeral range. At twitter, this manifests in connection-heavy jobs using the full ephemeral range. In turn, any executors we attempt to run after this point cannot bind to an ephemeral port.
We should explore enforcement of fair-sharing of ports, not sure how this ties into providing each executor with its own networking stack. This may be unnecessary in the long term depending on how we implement network isolation.
--
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