[
https://issues.apache.org/jira/browse/MESOS-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321212#comment-15321212
]
Tom Ganem commented on MESOS-3014:
----------------------------------
So I can see this issue is not a priority to anyone right now, but it is of
extreme interest to me. The company I work for specializes in high speed file
transfers. We have recently been brainstorming about creating a mesos framework
that would launch short-lived transfer processes on the mesos cluster. If
outbound network bandwidth was offered as a resource, we could ensure that each
transfer process we launch would have a desired amount of bandwidth while not
affecting other processes/containers.
> Support network egress bandwidth as a first-class resource
> ----------------------------------------------------------
>
> Key: MESOS-3014
> URL: https://issues.apache.org/jira/browse/MESOS-3014
> Project: Mesos
> Issue Type: Improvement
> Components: isolation
> Reporter: Adam B
> Labels: isolation, network, resource
>
> Mesos 0.23.0 introduced `--egress_rate_limit_per_container=100MB` for
> statically configuring a fixed, per-container limit on outbound network
> bandwidth, but if this were instead a standard resource type (outbound
> network bandwidth) with a fixed total, then different subsets could be
> reserved/claimed by different frameworks/tasks. This would allow us to adjust
> the per-container limit depending on how many containers are running, or give
> some containers more bandwidth than others.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
