hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5784) The length of the heartbeat cycle should be configurable.
Date Thu, 01 Oct 2009 08:08:23 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hemanth Yamijala updated HADOOP-5784:
-------------------------------------

    Release Note: Introduced a configuration parameter, mapred.heartbeats.in.second, as an
expert option, that defines how many heartbeats a jobtracker can process in a second. Administrators
can set this to an appropriate value based on cluster size and expected processing time on
the jobtracker to achieve a balance between jobtracker scalability and latency of jobs.

> The length of the heartbeat cycle should be configurable.
> ---------------------------------------------------------
>
>                 Key: HADOOP-5784
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5784
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Owen O'Malley
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-5784_yhadoop20.patch, patch-5784-1.txt, patch-5784.txt
>
>
> Currently, the hearbeat cycle is set to (# nodes / 100) in seconds. This can be too long
for clusters that need to run low latency jobs. We should make the number of heartbeats that
should arrive a second configurable.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message