[
https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075860#comment-15075860
]
Rohith Sharma K S commented on YARN-4479:
-----------------------------------------
Discussed offline with [~jianhe] for sync up and for the solution. The summary
is follows and respective patch updated.
# For failed attempt, while recovering need not to add to scheduler. Necessary
changes is done at RMAppAttemptImpl
# If attempts are added to scheduler means attempts were running before RM
restart.
# Any recovering attempts are added to new ordering policy
{{pendingOrderingPolicyRecovery}} which is given higher preference than
{{pendingOrderingPolicy}} while activating the applications.
> 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
> Attachments: 0001-YARN-4479.patch, 0002-YARN-4479.patch,
> 0003-YARN-4479.patch, 0004-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)
