hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5784) The length of the heartbeat cycle should be configurable.
Date Wed, 27 May 2009 06:18:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713435#action_12713435

Amar Kamat commented on HADOOP-5784:

Wondering which one is more intuitive, _number-of-heartbeats-per-sec_ or _heartbeat-interval_.
The title says _heartbeat-interval_ should be configurable whereas the description states
_number-of-heartbeats-per-sec_ should be configurable. I personally think _heartbeat-interval_
is easier to set and play around. Thoughts? 

Regarding the test case, cant we spoof tasktracker status and invoke JobTracker.heartbeat()
? This way we can increment the tracker count and query the jobtracker for the current heartbeat
interval? Thoughts?

> The length of the heartbeat cycle should be configurable.
> ---------------------------------------------------------
>                 Key: HADOOP-5784
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5784
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.21.0
>         Attachments: 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.

View raw message