[
https://issues.apache.org/jira/browse/HADOOP-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604624#action_12604624
]
Hadoop QA commented on HADOOP-3531:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12383920/3531.patch
against trunk revision 667040.
+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/2649/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2649/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2649/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2649/console
This message is automatically generated.
> Hod does not report job tracker failure on hod client side when job tracker
> fails to come up
> ---------------------------------------------------------------------------------------------
>
> Key: HADOOP-3531
> URL: https://issues.apache.org/jira/browse/HADOOP-3531
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/hod
> Affects Versions: 0.18.0
> Reporter: Karam Singh
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: 3531.patch
>
>
> Hod does not report job tracker failure on hod client side when job tracker
> fails to come up.
> When max-master-failure > 1
> hod client does not properly show why job tracker failed to come up, while in
> case namenode proper error message is displayed.
> Also in namenode failure ringmaster log contains information such as -:
> "Detected errors (3) beyond allowed number of failures (2). Flagging error to
> client"
> while no such information is there in ringmaster log for job tracker failures
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
