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

Eric Payne commented on YARN-2896:
----------------------------------

[~sunilg], it seems to me that labels can make things more confusing, not less, 
since different queues can have arbitrary names for the same concept. Also, it 
would eliminate the need to add an infrastructure for mapping, passing, and 
interpreting labels and priority numbers. YARN could always specify that 
priorities go from low to high, and each queue could then decide how hight to 
go with the priority numbers. Also, it seems to me that the following property 
definition could specify high priority:
{code}
yarn.scheduler.capacity.root.queueA.5.acl=user1,user2
{code}

> Server side PB changes for Priority Label Manager and Admin CLI support
> -----------------------------------------------------------------------
>
>                 Key: YARN-2896
>                 URL: https://issues.apache.org/jira/browse/YARN-2896
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, resourcemanager
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: 0001-YARN-2896.patch, 0002-YARN-2896.patch, 
> 0003-YARN-2896.patch, 0004-YARN-2896.patch
>
>
> Common changes:
>  * PB support changes required for Admin APIs 
>  * PB support for File System store (Priority Label Store)



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

Reply via email to