[
https://issues.apache.org/jira/browse/HADOOP-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542547
]
Doug Cutting commented on HADOOP-1900:
--------------------------------------
I don't see why finding an optimal heartbeat time is critical. Scaling as the
cluster grows seems reasonable, and using a safe scaling factor so that the
jobtracker is not overwhelmed even on slow hardware seems prudent. But I don't
see the importance of faster heartbeats on faster hardware, especially if it
adds complexity to the code. Unless someone can provide a reason why this is
important, I also feel an adaptive mechanism is overkill.
> the heartbeat and task event queries interval should be set dynamically by
> the JobTracker
> -----------------------------------------------------------------------------------------
>
> Key: HADOOP-1900
> URL: https://issues.apache.org/jira/browse/HADOOP-1900
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Reporter: Owen O'Malley
> Assignee: Amareshwari Sri Ramadasu
> Attachments: patch-1900.txt, patch-1900.txt
>
>
> The JobTracker should scale the intervals that the TaskTrackers use to
> contact it dynamically, based on how the busy it is and the size of the
> cluster.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
