[
https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066317#comment-15066317
]
Naganarasimha G R commented on YARN-4479:
-----------------------------------------
Hi [~rohithsharma],
As discussed offline,
Assume b4 recovery Apps which were activated :
*A1*(Low),*A2*(Low),*A3*(Medium) and pending were *A4*(High) & *A5*(High)
Based on the current approach applications will be activated in the order
*A4,A5,A3,A1,A2*
After your patch it will be *A3,A1,A2,A4,A5*
So in a way its better than the existing approach but wanted to know whether
the order of activation should be *A1, A2, A3* itself and not based on the
ordering policy for the recovered apps, Thoughts ?
IIUC [~sunilg] also wanted to say the same ?
> 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)
