[jira] [Commented] (MESOS-431) Port isolation / sharing in the ephemeral range.

["Jie Yu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083104#comment-14083104 ] 

Jie Yu commented on MESOS-431:
------------------------------

We can close this once network monitoring is resolved.

> Port isolation / sharing in the ephemeral range.
> ------------------------------------------------
>
>                 Key: MESOS-431
>                 URL: https://issues.apache.org/jira/browse/MESOS-431
>             Project: Mesos
>          Issue Type: Story
>          Components: isolation
>            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 was sent by Atlassian JIRA
(v6.2#6252)