[ https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074779#comment-15074779 ]
Rohith Sharma K S commented on YARN-4479: ----------------------------------------- I think we can just relay on isAppRecovering flag which should be sufficient. And existing code in RMAppAttemptImpl can be there as-it-is(without patch). Only FAILED attempts are added to scheduler which will be removed in next event itself. > 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 > > > 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)