[
https://issues.apache.org/jira/browse/YARN-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576208#comment-13576208
]
Siddharth Seth commented on YARN-365:
-------------------------------------
Xuan, took a quick look at the patch. I'm not sure why the NodeStatusUpdate
event needs to be generated in all the additional cases. It may just be
sufficient to drop the stored node updates - or even let them be processed by
the event which is already in the queue.
Also, within the schedulers - the events can be aggregated into a single list
and processed, instead of processing them per heartbeat.
> Each NM heartbeat should not generate and 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
> Attachments: Prototype2.txt, Prototype3.txt, YARN-365.1.patch,
> YARN-365.2.patch, YARN-365.3.patch, YARN-365.4.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
