You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2010/12/27 03:04:47 UTC
[jira] Updated: (MAPREDUCE-1906) Lower minimum heartbeat interval
for tasktracker > Jobtracker
[ https://issues.apache.org/jira/browse/MAPREDUCE-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated MAPREDUCE-1906:
-----------------------------------
Attachment: mapreduce-1906.txt
This is Scott's patch but also makes the minimum interval configurable. I set the default to 300ms as Scott suggests.
> Lower minimum heartbeat interval for tasktracker > Jobtracker
> -------------------------------------------------------------
>
> Key: MAPREDUCE-1906
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1906
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 0.20.1, 0.20.2
> Reporter: Scott Carey
> Attachments: MAPREDUCE-1906-0.21.patch, mapreduce-1906.txt
>
>
> I get a 0% to 15% performance increase for smaller clusters by making the heartbeat throttle stop penalizing clusters with less than 300 nodes.
> Between 0.19 and 0.20, the default minimum heartbeat interval increased from 2s to 3s. If a JobTracker is throttled at 100 heartbeats / sec for large clusters, why should a cluster with 10 nodes be throttled to 3.3 heartbeats per second?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.