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

Sidharta Seethana commented on YARN-3365:
-----------------------------------------

Example tc usage :

Lets say that we need to read the 'state' of the network interface w.r.t the 
traffic shaping rules and classes in place. We'll invoke {[container-executor}} 
in the following manner {{container-executor --read-state  
tmp-file-with-tc-commands.txt}} . {{container-executor}} in turn invokes 
{{/sbin/tc -b tmp-file-with-tc-commands.txt}} . The contents of the temporary 
file contain "show" instructions like these 

{quote}
qdisc show dev eth0
filter show dev eth0
class show dev eth0
{quote}

The output from tc for such a batch of commands would look like this :

{quote}
qdisc htb 42: root refcnt 2 r2q 10 default 0 direct_packets_stat 27
filter parent 42: protocol ip pref 10 cgroup handle 0x1

filter parent 42: protocol ip pref 10 cgroup handle 0x1

class htb 42:1 root rate 100000Kbit ceil 100000Kbit burst 1600b cburst 1600b
class htb 42:2 parent 42:1 prio 0 rate 2000Kbit ceil 100000Kbit burst 1600b 
cburst 1600b
class htb 42:3 parent 42:1 prio 0 rate 2000Kbit ceil 100000Kbit burst 1600b 
cburst 1600b
{quote}




> Add support for using the 'tc' tool via container-executor
> ----------------------------------------------------------
>
>                 Key: YARN-3365
>                 URL: https://issues.apache.org/jira/browse/YARN-3365
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>            Reporter: Sidharta Seethana
>            Assignee: Sidharta Seethana
>         Attachments: YARN-3365.001.patch, YARN-3365.002.patch
>
>
> We need the following functionality :
> 1) modify network interface traffic shaping rules - to be able to attach a 
> qdisc, create child classes etc
> 2) read existing rules in place 
> 3) read stats for the various classes 
> Using tc requires elevated privileges - hence this functionality is to be 
> made available via container-executor. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to