[ https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109985#comment-15109985 ]
Naganarasimha G R commented on YARN-4479: ----------------------------------------- Thanks for pointing out [~wangda], bq. Instead of using queue's configured ordering-policy for pending apps, it should use FifoOrderingPolicyForPendingApps. Yes and having {{FairOrderingPolicy}} for the pending apps does not make sense as the {{getCachedUsed}} will be always zero . And as you said currently we can keep it fixed policy for now as there no real world need to make pending queues configurable. So i am ok with this approach . > 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)