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 "Amar Kamat (JIRA)" <ji...@apache.org> on 2008/12/04 13:21:44 UTC

[jira] Commented: (HADOOP-4772) Combine TaskTracker information into single class in JobTracker

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

Amar Kamat commented on HADOOP-4772:
------------------------------------

+1. I feel its right time to fix HADOOP-3343 also. Something like {{TrackerID}} and {{TrackerManager}}.

> Combine TaskTracker information into single class in JobTracker
> ---------------------------------------------------------------
>
>                 Key: HADOOP-4772
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4772
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Sharad Agarwal
>
> Currently tracker related information is spanned thru multiple datastructures. eg. trackerToTaskMap, trackerToMarkedTasksMap, trackerToHeartbeatResponseMap etc. These are hard to maintain. It would be efficient (as there won't be multiple searches in TreeSet) and much more manageable code if we create a single class say TrackerInfo; and just have one map of trackerId to TrackerInfo

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