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 "Daniel Templeton (JIRA)" <ji...@apache.org> on 2016/06/14 17:48:27 UTC
[jira] [Updated] (YARN-4143) Optimize the check for AMContainer
allocation needed by blacklisting and ContainerType
[ https://issues.apache.org/jira/browse/YARN-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Templeton updated YARN-4143:
-----------------------------------
Attachment: YARN-4143.002.patch
Since [~adhoot] doesn't seem to be working on this one anymore, I just rebased it and posted a new patch. This patch turns out to be considerably simpler than its predecessor because some of the cleanup that was in the original patch made it in already. [~sunilg], wanna have a look?
> 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: Daniel Templeton
> Attachments: YARN-4143.001.patch, YARN-4143.002.patch
>
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org