[
https://issues.apache.org/jira/browse/MESOS-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159415#comment-15159415
]
Jie Yu commented on MESOS-4738:
-------------------------------
Thank you for filing the ticket. This is something we were thinking about. One
question I have is: bandwidth is the kind of the resources that we always want
to oversubscribe. For instance, if there are 100 containers on an agent with 1G
NIC, I do not want my container bandwidth to be capped at 10M. I still want
full bandwidth if no one is using the network. Does that mean that framework
needs to be oversubscription aware? Do we need to introduce priority for
network?
> Make ingress and egress bandwidth a resource
> --------------------------------------------
>
> Key: MESOS-4738
> URL: https://issues.apache.org/jira/browse/MESOS-4738
> Project: Mesos
> Issue Type: Improvement
> Reporter: Sargun Dhillon
> Priority: Minor
> Labels: mesosphere
>
> Some of our users care about variable network network isolation. Although we
> cannot fundamentally limit ingress network bandwidth, having it as a
> resource, so we can drop packets above a specific limit would be attractive.
> It would be nice to expose egress and ingress bandwidth as an agent resource,
> perhaps with a default of 10,000 mbps, and we can allow people to adjust as
> needed. Alternatively, a more advanced design would involve generating
> heuristics based on an analysis of the network MII / PHY.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
