[
https://issues.apache.org/jira/browse/YARN-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15066571#comment-15066571
]
Naganarasimha G R commented on YARN-4479:
-----------------------------------------
Thanks [~sunilg],
bq. Its debatable and I think with discussion we can conclude the approach here.
True its debate-able, but one more thing to be considered(/not missed) here A4
and A5 gets activated even before A2 (as per the correction i mentioned).
bq. {{All containers which were running earlier will still continue}}
I mistook what you meant, it seems like you got what i wanted to mention.
> 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)
