hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anubhav Dhoot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4143) Optimize the check for AMContainer allocation needed by blacklisting and ContainerType
Date Thu, 17 Sep 2015 19:47:04 GMT

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

Anubhav Dhoot commented on YARN-4143:
-------------------------------------

I think we can minimize the impact of checking on every allocate to only allocates before
the AM is assigned which should be only a few times until AM itself gets launched. This avoids
adding an API to the scheduler.

> Optimize the check for AMContainer allocation needed by blacklisting and ContainerType
> --------------------------------------------------------------------------------------
>
>                 Key: YARN-4143
>                 URL: https://issues.apache.org/jira/browse/YARN-4143
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Anubhav Dhoot
>            Assignee: Anubhav Dhoot
>
> In YARN-2005 there are checks made to determine if the allocation is for an AM container.
This happens in every allocate call and should be optimized away since it changes only once
per SchedulerApplicationAttempt



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

Mime
View raw message