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

Naganarasimha G R commented on YARN-4479:
-----------------------------------------

In Most cases this would be sufficient, but consider a case where in A3 is an 
app with large number of containers and A1 and A2 are short jobs. May be after 
recovery all nodes have not registered, due to AM resource limits A1 and/or A2 
AM's resource if activated will exceed AM's resource limits, so only A3 will be 
running. Problem here is : there is no configurable ordering policy for 
recovered apps seperately, it applies the same policy so in rare cases it might 
lead to starvation ?

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