You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Arun C Murthy (JIRA)" <ji...@apache.org> on 2008/07/31 03:28:31 UTC

[jira] Commented: (HADOOP-3875) Fix TaskTracker's heartbeat timer to note the time the hearbeat RPC returned to decide next heartbeat time

    [ https://issues.apache.org/jira/browse/HADOOP-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618579#action_12618579 ] 

Arun C Murthy commented on HADOOP-3875:
---------------------------------------

Also, there is a redundant call to System.currentTime in TaskTracker.transmitHeartbeat - that information is already available at TaskTracker.offerService, we should just pass it down.

> Fix TaskTracker's heartbeat timer to note the time the hearbeat RPC returned to decide next heartbeat time
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3875
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3875
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.18.0
>            Reporter: Arun C Murthy
>            Assignee: Arun C Murthy
>             Fix For: 0.19.0
>
>
> The tasktracker notes the time the heartbeat RPC was fired, rather than when it returned to decide when to send the next one. If the RPC spends a lot of time in the JobTracker's queue then the above exacerbates the load on the JobTracker.

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