Sunil G commented on YARN-2896:

Thank you [~eepayne] and [~wangda] for the comments

The idea of keeping Application Priority as a string is for better handling and 
for easiness from user perspective.
Internally RM will have a corresponding integer mapping, and only that will be 
used by Schedulers. Hence as wangda mentioned, it can be operated just like an 
integer with user priority etc.

A rough idea is like, user is submitting a job with priority as “High” and 
scheduler will be treating as an integer namely “3”.
Priority Label Manager will act as an interface to User and Scheduler and can 
give the priority as string or integer accordingly.

Now coming to the advantages, admin can operate on names or labels for 
priority, it will be easier. Also it can be displayed in UI very easily.
Also admin can config the priority label as per his norms along by defining 
corresponding integer mapping associated with each label.
For eg:
Configuring ACLs based on a priority label name will be more easier.

Please share your thoughts.
I will address the other comments from Eric and will update a patch.

> 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

Reply via email to