[
https://issues.apache.org/jira/browse/YARN-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588861#comment-13588861
]
Xuan Gong commented on YARN-365:
--------------------------------
bq:Do we need to worry about there being overlap between the 2 lists. i.e. a
newlyLaunchedContainer also got completed by the time the slow RM handled the
NM updates?
Thanks for the comments. I think we are fine here. The way to handle
newlyLaunchedContainers is to submit a LAUNCHED event to RMContainerImpl, and
RMContainerImpl will unregister(remove) this container from
containerAllocationExpirer list. That is how we handle the
newlyLaunchedContainers. It does not actually launch the container. Just tell
the RM that this container is being used right now.
> Each NM heartbeat should not generate an event for the Scheduler
> ----------------------------------------------------------------
>
> Key: YARN-365
> URL: https://issues.apache.org/jira/browse/YARN-365
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager, scheduler
> Affects Versions: 0.23.5
> Reporter: Siddharth Seth
> Assignee: Xuan Gong
> Fix For: 2.0.4-beta
>
> Attachments: Prototype2.txt, Prototype3.txt, YARN-365.10.patch,
> YARN-365.1.patch, YARN-365.2.patch, YARN-365.3.patch, YARN-365.4.patch,
> YARN-365.5.patch, YARN-365.6.patch, YARN-365.7.patch, YARN-365.8.patch,
> YARN-365.9.patch
>
>
> Follow up from YARN-275
> https://issues.apache.org/jira/secure/attachment/12567075/Prototype.txt
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
