[
https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109057#comment-15109057
]
Jian He commented on YARN-4479:
-------------------------------
[~rohithsharma], I think we had same discussion offline whether it's worth for
pendingApps to have its own ordering policy. But it was then crossed off. What
was the reason ? Is it because we thought pending apps and active apps should
share most policy ? Now I agree this approach is better, if we agree that
pending apps can just be treated separately,
> 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)
