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

["Ian Downes (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Downes resolved MESOS-431.
------------------------------
    Resolution: Fixed

Fixed by the port_mapping network isolator.

> 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.3.4#6332)