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

Daniel Templeton commented on YARN-2497:
----------------------------------------

The primary motivation for queue labels is to allow for access control of 
labeled resources.  If we don't allow labels at the queue level, we have to 
live without ACLs or build support for ACLs into node labels, which is a pretty 
big change.

There are certainly new issues that will crop up because of node labels.  For 
example, we can block an app from going into a queue that doesn't offer the 
labels it says it needs, but we can't do anything about the app making resource 
requests with labels that the queue doesn't support.  In that case the requests 
will simply remain pending forever because the queue will not accept any node 
that doesn't have a compatible label.  I looked at how to mitigate that issue 
specifically, and I don't see anything that's not a significant overhaul of the 
way things work today.  Capacity scheduler has the same issue, and thus far it 
doesn't sound like it has been a big problem.

> Changes for fair scheduler to support allocate resource respect labels
> ----------------------------------------------------------------------
>
>                 Key: YARN-2497
>                 URL: https://issues.apache.org/jira/browse/YARN-2497
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: fairscheduler
>            Reporter: Wangda Tan
>            Assignee: Daniel Templeton
>         Attachments: YARN-2497.001.patch, YARN-2497.002.patch, 
> YARN-2497.003.patch, YARN-2497.004.patch, YARN-2497.005.patch, 
> YARN-2497.006.patch, YARN-2497.007.patch, YARN-2497.008.patch, 
> YARN-2497.009.patch, YARN-2497.010.patch, YARN-2499.WIP01.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to