[
https://issues.apache.org/jira/browse/YARN-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753093#comment-13753093
]
Siddharth Seth commented on YARN-1067:
--------------------------------------
I think it'll be useful to have a minimum - i.e. wait for at least this minimum
time before sending another heartbeat, irrespective of whether a resource
request is pending or not. Gives the RM time to actually allocate some
containers, for the AM to attempt an allocation of these containers, and is
possibly better for the consistency of tables maintained by the AM and RM.
Also the heartbeat interval could be scaled back - higher than the minimum if
there's no allocations.
Could some of the sleeps be replaced with wait/notify ?
> AMRMClient heartbeat interval should not be static
> --------------------------------------------------
>
> Key: YARN-1067
> URL: https://issues.apache.org/jira/browse/YARN-1067
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.0.5-alpha
> Reporter: Siddharth Seth
> Attachments: YARN-1067.patch
>
>
> The heartbeat interval can be modified dynamically - more often when there
> are pending requests, and toned down when the heartbeat is solving no purpose
> other than a ping.
> There's a couple of jiras which are trying to change the scheduling loop - at
> which point this becomes useful.
--
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
