[
https://issues.apache.org/jira/browse/YARN-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572893#comment-13572893
]
Thomas Graves commented on YARN-365:
------------------------------------
So I'm not sure that this is gaining us anything. The scheduler still has the
same amount of work to do. Its either doing it one at a time via multiple
events or with these changes all at once but processing the same number in the
list of things stored in the RMNode. I can see cases where the all at once is
actually worse as it will spend more time on a single heartbeat and potentially
not get to other things in the queue like apps added as fast.
The only way I can see this being beneficial is if we can aggregate the
heartbeats and have the scheduler process less.
> 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
>
>
> 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
