Wangda Tan commented on YARN-3216:

Thanks for sharing your thoughts, [~sunilg], [~Naganarasimha].
Reconsidered this problem, I prefer to go with option-2, partition should be 
considered as a sub-cluster, so it should have its own 
max-am-resource-percentage. I think what we can do is:
- Have a per-queue-per-partition "max am percentage" configuration, if it not 
specific, we assume it inherits queue's configured one.
- We guarantee to launch at least one AM container in every partition no matter 
which is the AM-resource-percentage setting.
- If we change node's label, we should update per-queue-per-partition-am-used 
resource as well. (We have YARN-4082 committed).

Sounds like a plan? :)

> 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: Sunil G
>            Priority: Critical
>         Attachments: 0001-YARN-3216.patch
> 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

Reply via email to