[
https://issues.apache.org/jira/browse/HADOOP-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602033#action_12602033
]
Hadoop QA commented on HADOOP-236:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12383007/236_v1.patch
against trunk revision 662813.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2547/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2547/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2547/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2547/console
This message is automatically generated.
> job tracker should refuse connection from a task tracker with a different
> version number
> ----------------------------------------------------------------------------------------
>
> Key: HADOOP-236
> URL: https://issues.apache.org/jira/browse/HADOOP-236
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.2.1
> Reporter: Hairong Kuang
> Assignee: Sharad Agarwal
> Fix For: 0.18.0
>
> Attachments: 236_v1.patch
>
>
> After one mapred system upgrade, we noticed that all tasks assigned to one
> task tracker failed. It turned out that for some reason the task tracker was
> not upgraded.
> To avoid this, a task tracker should reports its version # when it registers
> itsself with a job tracker. If the job tracker receives an inconsistent
> version #, it should refuse the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
