You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2016/02/23 00:02:18 UTC
[jira] [Commented] (MESOS-4738) Make ingress and egress bandwidth a
resource
[ https://issues.apache.org/jira/browse/MESOS-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157896#comment-15157896 ]
Adam B commented on MESOS-4738:
-------------------------------
Have you tried this with custom resource types yet? Does that work for you?
I'm not sure we should first-class a new resource type unless we can measure and isolate it.
> 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)