[
https://issues.apache.org/jira/browse/YARN-10617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281535#comment-17281535
]
Sunil G commented on YARN-10617:
--------------------------------
Hi [~ananyo_rao]
Yes. In the preemption module, we get all apps from the scheduler. Hence some
of the apps may be in a pending state which cant be scheduled (due to AM limit
etc). So I think this is a quick fix.
> Fifo and Fair intra-queue preemption goes on indefinitely when apps are in
> pending state due to max AM limit reached
> --------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-10617
> URL: https://issues.apache.org/jira/browse/YARN-10617
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler
> Affects Versions: 3.1.1
> Reporter: VADAGA ANANYO RAO
> Assignee: VADAGA ANANYO RAO
> Priority: Major
> Attachments: YARN-10617.patch
>
>
> This case occurs when:
> 1. an application gets submitted in a cluster running at max-AM limit.
> 2. The new job requests AM resource. So it has 1 pending request.
> 3. To fulfil this request, the preemption logic preempts 1 resource from a
> running app.
> 4. Because the cluster is at max-AM limit, the scheduler re-assigns the
> preempted container back to the running app.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
