Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-431

Port isolation / sharing in the ephemeral range.

    XMLWordPrintableJSON

Details

    • Story
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • containerization
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              bmahler Benjamin Mahler
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: