hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Kandula (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3366) Outbound network bandwidth : classify/shape traffic originating from YARN containers
Date Wed, 03 Jun 2015 23:21:39 GMT

    [ https://issues.apache.org/jira/browse/YARN-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571821#comment-14571821

Srikanth Kandula commented on YARN-3366:

1) Does this also capture the network usage due to non containers? For eg. that due to evacuation
or replication or data downloads? 

2) What about receive bandwidth?

3) Perhaps i missed this above, but what are the overhead microbenchmark numbers re: added
latency for normal packets and extra cpu usage overall due to sending packets through tc/
due to polling tc counters periodically?

> Outbound network bandwidth : classify/shape traffic originating from YARN containers
> ------------------------------------------------------------------------------------
>                 Key: YARN-3366
>                 URL: https://issues.apache.org/jira/browse/YARN-3366
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Sidharta Seethana
>            Assignee: Sidharta Seethana
>             Fix For: 2.8.0
>         Attachments: YARN-3366.001.patch, YARN-3366.002.patch, YARN-3366.003.patch, YARN-3366.004.patch,
YARN-3366.005.patch, YARN-3366.006.patch, YARN-3366.007.patch
> In order to be able to isolate based on/enforce outbound traffic bandwidth limits, we
need  a mechanism to classify/shape network traffic in the nodemanager. For more information
on the design, please see the attached design document in the parent JIRA.

This message was sent by Atlassian JIRA

View raw message