mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cong Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-4738) Make ingress and egress bandwidth a resource
Date Tue, 23 Feb 2016 19:55:18 GMT

    [ https://issues.apache.org/jira/browse/MESOS-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159541#comment-15159541
] 

Cong Wang commented on MESOS-4738:
----------------------------------

We don't have a mechanism to shape the ingress bandwidth, so here it should be egress only.

> 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)

Mime
View raw message