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 "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2008/12/19 10:59:46 UTC
[jira] Commented: (HADOOP-4869) Lost Trackers may not be able to
join back
[ https://issues.apache.org/jira/browse/HADOOP-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658047#action_12658047 ]
Amareshwari Sriramadasu commented on HADOOP-4869:
-------------------------------------------------
test-patch result:
[exec]
[exec]
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new or modified tests.
[exec] Please justify why no tests are needed for this patch.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
[exec]
> Lost Trackers may not be able to join back
> ------------------------------------------
>
> Key: HADOOP-4869
> URL: https://issues.apache.org/jira/browse/HADOOP-4869
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Devaraj Das
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: patch-4869.txt
>
>
> There is a bug in the heartbeat processing which shows up when TaskTrackers are lost. Due to the bug, lost TTs may not be able to join back the JT after reinitializing (and binding to a RPC port different from the previous one). This bug got introduced in HADOOP-4305.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.