[ 
https://issues.apache.org/jira/browse/YARN-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sunil G updated YARN-3093:
--------------------------
    Description: 
Proposing "yarn rmadmin -load -nodelabels <filename>"

"nodelabels" can be one such option here, and this can be generalized by giving 
other options later.
Advantage of this command will be an easier configuration. Assume admin need to 
load labels to more than 20+ nodes, current command is little difficult. If 
these config can be preloaded in a file, and then can upload to RM. With 
existing parsing and update logic, same can be achieved.

I am showing a simpler proposed config file.
{noformat}
rm1 $ cat node_label.conf
add [
label1,label2,label3,label4,label11,label12,label13,label14,abel21,label22,label23,label24
]  
replace[
node1:port=label1,label2,label23,label24
node2:port=label4,abel11,label12,label13,label14,label21
node3:port=label2,label3,label4,label11,label12,label13,label14
node4:port=label14,abel21,label22,label23,label24
node5:port=label14,abel21,label22,label23,label24
node6:port=label4,abel11,label12,label13,label14,label21,label22,label23,label24
]
{noformat}

A restriction on file size can be kept to avoid uploading very huge files. 

Please share your opinion.

  was:Proposing "yarn rmadmin -load -nodelabels <filename>"


> Support load command from admin [Helps to load big set of labels]
> -----------------------------------------------------------------
>
>                 Key: YARN-3093
>                 URL: https://issues.apache.org/jira/browse/YARN-3093
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Sunil G
>            Assignee: Sunil G
>
> Proposing "yarn rmadmin -load -nodelabels <filename>"
> "nodelabels" can be one such option here, and this can be generalized by 
> giving other options later.
> Advantage of this command will be an easier configuration. Assume admin need 
> to load labels to more than 20+ nodes, current command is little difficult. 
> If these config can be preloaded in a file, and then can upload to RM. With 
> existing parsing and update logic, same can be achieved.
> I am showing a simpler proposed config file.
> {noformat}
> rm1 $ cat node_label.conf
> add [
> label1,label2,label3,label4,label11,label12,label13,label14,abel21,label22,label23,label24
> ]  
> replace[
> node1:port=label1,label2,label23,label24
> node2:port=label4,abel11,label12,label13,label14,label21
> node3:port=label2,label3,label4,label11,label12,label13,label14
> node4:port=label14,abel21,label22,label23,label24
> node5:port=label14,abel21,label22,label23,label24
> node6:port=label4,abel11,label12,label13,label14,label21,label22,label23,label24
> ]
> {noformat}
> A restriction on file size can be kept to avoid uploading very huge files. 
> Please share your opinion.



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

Reply via email to