[
https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108323#comment-15108323
]
Wangda Tan commented on YARN-4479:
----------------------------------
Hi [~sunilg]/[~rohithsharma],
Please note one of my comment above:
{code}
Instead of using queue's configured ordering-policy for pending apps, it should
use FifoOrderingPolicyForPendingApps.
with the change, user cannot configure ordering-policy for pending-apps, I
didn't see a strong real life requirement for that now.
{code}
I think we still need to treat ordering policy of pending apps specially, and
with the new added FifoOrderingPolicyForPendingApps, we don't need to reset
isRecoverying and other ordering policies don't need the isRecoverying field,
so it won't affect performance.
bq. 2. With new FifoOrderingPolicyForPendingApps, we are agreeing that Priority
and Submission Time will be factor to decide pending apps ordering, correct?
Yes, the only difference between FifoOrderingPolicyForPendingApps and
FifoOrderingPolicy is FifoOrderingPolicyForPendingApps let recovering apps go
first.
> 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)
