[
https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108310#comment-15108310
]
Rohith Sharma K S commented on YARN-4479:
-----------------------------------------
Hi [~leftnoteasy]
There were 2 approaches to solve this
# Handle this problem in upper layer i.e LeafQueue layer nevertheless of any
ordering
policy.[0006-YARN-4479.patch|https://issues.apache.org/jira/secure/attachment/12780671/0006-YARN-4479.patch]
# Handle in very bottom layer i.e specific to ordering policy. If any new
ordering policy added then that has to take care of this JIRA problem.
[0003-YARN-4479.patch|https://issues.apache.org/jira/secure/attachment/12779965/0003-YARN-4479.patch]
Issues in approach-2 is
## Performance : It does comparison for wasAttemptRecovering on every addition
or removal. When there are huge number of applications, it is significantly
impact.
## The flag need to reset while adding to activeApplication list.
> Retrospect app-priority in pendingOrderingPolicy during recovering
> applications
> -------------------------------------------------------------------------------
>
> Key: YARN-4479
> URL: https://issues.apache.org/jira/browse/YARN-4479
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api, resourcemanager
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Fix For: 2.8.0
>
> Attachments: 0001-YARN-4479.patch, 0002-YARN-4479.patch,
> 0003-YARN-4479.patch, 0004-YARN-4479.patch, 0004-YARN-4479.patch,
> 0005-YARN-4479.patch, 0006-YARN-4479.patch
>
>
> Currently, same ordering policy is used for pending applications and active
> applications. When priority is configured for an applications, during
> recovery high priority application get activated first. It is possible that
> low priority job was submitted and running state.
> This causes low priority job in starvation after recovery
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
