[
https://issues.apache.org/jira/browse/YARN-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900613#comment-14900613
]
Sunil G commented on YARN-4143:
-------------------------------
Yes [~adhoot]. I am also not getting any other way other than this Event
handling. Because RMAppAttempt need to update such information to Schedulers
(common), and either an Event or an API is only a clean way here.
I do not have any objection here for existing way what is done in the patch.
Thought of bringing up all possible options here and weigh in the best.
> 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
> Attachments: YARN-4143.001.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)
