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

Wangda Tan commented on YARN-796:
---------------------------------

bq. You can solve this problem today by just running separate RMs.
I think it's not good for configure, user need maintain several configuration 
folders in their nodes for submission job.

bq. In practice, however, marking nodes for specific teams in queue systems 
doesn't work because doing so assumes that the capacity never changes... i.e
It is possible that you cannot replace a failure node by a random node in 
heterogeneous cluster. E.g. only some nodes have GPUs, and these nodes will be 
dedicated to be used by data scientist team. Percentage of queue capacity 
doesn't make a lot of sense here. 

bq. ... except, you guessed it: this is a solved problem today too. You just 
need to make sure the container sizes that are requested consume the whole node.
Assume a HBase master want to run a node have 64G mem and infiniband. You can 
ask a 64G mem container, but it may be like to be allocated to a 128G node but 
doesn't have infiniband.
Again, it's another heterogeneous issue.
And ask for such a big container may need take a great amount of time, wait for 
resource reservation, etc.

bq. it still wouldn't be a nightmare because any competent admin would use 
configuration management to roll out changes to the nodes in a controlled 
manner.
It is very likely not every admin has scripts like you, especially some new 
YARN users, we'd better make this feature can be used out-of-box

> Allow for (admin) labels on nodes and resource-requests
> -------------------------------------------------------
>
>                 Key: YARN-796
>                 URL: https://issues.apache.org/jira/browse/YARN-796
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Arun C Murthy
>            Assignee: Wangda Tan
>         Attachments: LabelBasedScheduling.pdf, 
> Node-labels-Requirements-Design-doc-V1.pdf, YARN-796.patch
>
>
> It will be useful for admins to specify labels for nodes. Examples of labels 
> are OS, processor architecture etc.
> We should expose these labels and allow applications to specify labels on 
> resource-requests.
> Obviously we need to support admin operations on adding/removing node labels.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to