hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4869) Lost Trackers may not be able to join back
Date Fri, 19 Dec 2008 09:56:44 GMT

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

Amareshwari Sriramadasu updated HADOOP-4869:

    Attachment: patch-4869.txt

Attaching the patch that puts back heartbeat code which was prior to HADOOP-4305. 
Manually tested patch for the lost trackers trying to bind to different port. 
Also repeated manual tests mentioned for HADOOP-4305.

Tried to write a testcase for Lost tracker bouncing back, but that looks difficult.

> 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.

View raw message