[
https://issues.apache.org/jira/browse/HADOOP-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622526#action_12622526
]
Amareshwari Sriramadasu commented on HADOOP-3947:
-------------------------------------------------
test-patch result on trunk :
{code}
[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 appears to have generated 1
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]
{code}
-1 javadoc is known issue. HADOOP-3949
It's difficult to write testcase for this.
> TaskTrackers fail to connect back upon a re-init action
> -------------------------------------------------------
>
> Key: HADOOP-3947
> URL: https://issues.apache.org/jira/browse/HADOOP-3947
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Amar Kamat
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Attachments: HADOOP-3947-v1.patch, patch-3947.txt
>
>
> It seems that if the {{JobTracker}} asks the {{TaskTracker}} to re-initialize
> itself, the {{TaskTracker}} never connects back to the {{Jobtracker}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
