You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Wangda Tan (JIRA)" <ji...@apache.org> on 2015/07/17 23:22:04 UTC

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

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

Wangda Tan commented on YARN-3216:
----------------------------------

There're two approaches of doing that,
- Make maxAMResource = queue's-total-guaranteed-resource (Sum of queue's guaranteed resource on all partitions) * maxAmResourcePercent. It will be straightforward, but also can lead to too many AMs launched under a single partition.
- Make maxAMResource computed per queue per partition, this can make AM usages under partitions are more balanced, but can also lead to hard debugging (My application get stuck because of AMResourceLimit for a partition is violated).

I prefer 1st solution since it's easier to understand and debugging.

> Max-AM-Resource-Percentage should respect node labels
> -----------------------------------------------------
>
>                 Key: YARN-3216
>                 URL: https://issues.apache.org/jira/browse/YARN-3216
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>
> Currently, max-am-resource-percentage considers default_partition only. When a queue can access multiple partitions, we should be able to compute max-am-resource-percentage based on that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)