[
https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499401#comment-14499401
]
Sunil G commented on YARN-2003:
-------------------------------
HI [~leftnoteasy]
bq. authenticateApplicationPriority, I'm wondering if we really need it.
I understand your point. But we may fire a new APP_ADDED event from
RmAppManager to respective scheduler with a unapproved priority, and then
reject from there.
If we can do much earlier with help of a single api, it may avoid some extra
event handling in the case of wrong(invalid priority) app submission.
> Support to process Job priority from Submission Context in
> AppAttemptAddedSchedulerEvent [RM side]
> --------------------------------------------------------------------------------------------------
>
> Key: YARN-2003
> URL: https://issues.apache.org/jira/browse/YARN-2003
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: 0001-YARN-2003.patch, 0002-YARN-2003.patch,
> 0003-YARN-2003.patch, 0004-YARN-2003.patch, 0005-YARN-2003.patch,
> 0006-YARN-2003.patch
>
>
> AppAttemptAddedSchedulerEvent should be able to receive the Job Priority from
> Submission Context and store.
> Later this can be used by Scheduler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
