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

Sunil G commented on YARN-4479:
-------------------------------

Thanks [~leftnoteasy] for the detailed comment.
Yes, I understood the reason behind the same when FairOrderingPolicy is used. 
Generally fine with approach suggested. However few minor points.

1.
bq.Keep changes for SchedulerApplicationAttempt/CapacityScheduler in the patch: 
0006-YARN-4479.patch to set "isRecoverying" field
We already have a recovering field in SchedulerApplicationAttempt. But if we 
make use of this, we need to reset the flag once application is moved to 
{{activeApplications}} list. So if we reset this flag, we will loose 
information whether this was a recovered app. As of now I am not seeing any use 
with this, but it may confuse. So cud we introduce a new flag/field for this to 
avoid confusion.

2. With new FifoOrderingPolicyForPendingApps, we are agreeing that Priority and 
Submission Time will be factor to decide pending apps ordering, correct?


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

Reply via email to