hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6197) CS Leaf queue am usage gets updated for unmanaged AM
Date Mon, 20 Feb 2017 17:15:44 GMT

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

Varun Saxena commented on YARN-6197:

It seems to be a conscious decision made in YARN-2637. 
However, IMO unmanaged AMs' usage should not be counted towards queue's AM usage. Unmanaged
AMs' would be standalone processes(which user does not want to run as a YARN container) and
if an NM is running on the same node as the unmanaged AM is running on i.e. the node is to
be used for launching YARN containers, we can expect the admin to consider that while configuring
NM capability.

cc [~leftnoteasy]. Your thoughts on this?

> CS Leaf queue am usage gets updated for unmanaged AM
> ----------------------------------------------------
>                 Key: YARN-6197
>                 URL: https://issues.apache.org/jira/browse/YARN-6197
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Bibin A Chundatt
>            Assignee: Bibin A Chundatt
> {{LeafQueue#activateApplication()}} for unmanaged AM  the am_usage is updated with scheduler
minimum allocation size. Cluster resource/AM limit headroom for other apps in queue will get
reduced .
> Solution: FicaScheduler unManagedAM flag can be used to check AM type.
> Based on flag the queueusage need to be updated during activation and removal
> Thoughts??

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message