Sunil G updated YARN-2003:
    Attachment: 0022-YARN-2003.patch

Uploading a new version of patch after fixing test issues and warnings.

One more validation is added in CS. There are two cases 
- user submit a new application without specifying priority and submits to a 
non-existent queue.
- user submit a new application without specifying priority and submits with no 
queue (queue as null). Assuming that a queue mapping is done with this user in 
cs config file.

Validation for such cases are happening in addApplication in CS. But this will 
come only later in the call flow. To fill in the default priority from 
RMAppManager, we need the {{queue}} object. hence i added these checks in 
{{checkAndGetApplicationPriority}}. Please share your thoughts.

> Support for Application priority : Changes in RM and Capacity Scheduler
> -----------------------------------------------------------------------
>                 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, 00010-YARN-2003.patch, 
> 0002-YARN-2003.patch, 0003-YARN-2003.patch, 0004-YARN-2003.patch, 
> 0005-YARN-2003.patch, 0006-YARN-2003.patch, 0007-YARN-2003.patch, 
> 0008-YARN-2003.patch, 0009-YARN-2003.patch, 0011-YARN-2003.patch, 
> 0012-YARN-2003.patch, 0013-YARN-2003.patch, 0014-YARN-2003.patch, 
> 0015-YARN-2003.patch, 0016-YARN-2003.patch, 0017-YARN-2003.patch, 
> 0018-YARN-2003.patch, 0019-YARN-2003.patch, 0020-YARN-2003.patch, 
> 0021-YARN-2003.patch, 0022-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

Reply via email to