hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3216) Max-AM-Resource-Percentage should respect node labels
Date Mon, 10 Aug 2015 17:33:46 GMT

     [ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sunil G updated YARN-3216:
--------------------------
    Attachment: 0001-YARN-3216.patch

Hi [~leftnoteasy]
Attaching an initial version of work in progress patch. I used {{getAMResourceRequest}} from
RMApp to compare with container resource request to know whether its an AM Container from
FicaSchedulerApp.
{code}
+    if (request.equals(rmApp.getAMResourceRequest())) {
+      setAMResource(node.getPartition(), request.getCapability());
+    }
{code}

But I suspect a potential problem. If a buggy app submits a resource request which is similar
to the one which RM creates for AM request, then this check may be problematic. In that case
I feel i need an event from RMAppAttemptImpl where we detect AM container to Scheduler to
update the AM used resource details on specified partition. Cud u pls share your thoughts
on same.

> 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
>         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
(v6.3.4#6332)

Mime
View raw message