[ 
https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074705#comment-15074705
 ] 

Rohith Sharma K S commented on YARN-4479:
-----------------------------------------

bq. For finished attempt, I think we do not need to re-add into scheduler, so 
this whole code could be removed.
While recovering application and attempts, If the last attempt is FAILED then 
from scheduler transfer state from previous attempt. So, whenever there is 
failed attempt, attempt has to be added to scheduler for obtaining the state. 
Reference test case {{TestRMRestart#testRMRestartAppRunningAMFailed}}

> 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)

Reply via email to