Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 6874 invoked from network); 12 Jun 2008 19:53:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Jun 2008 19:53:07 -0000 Received: (qmail 84377 invoked by uid 500); 12 Jun 2008 19:53:08 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 84337 invoked by uid 500); 12 Jun 2008 19:53:08 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 84326 invoked by uid 99); 12 Jun 2008 19:53:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jun 2008 12:53:08 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jun 2008 19:52:27 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 18825234C139 for ; Thu, 12 Jun 2008 12:52:45 -0700 (PDT) Message-ID: <1460582989.1213300365099.JavaMail.jira@brutus> Date: Thu, 12 Jun 2008 12:52:45 -0700 (PDT) From: "Hadoop QA (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-3531) Hod does not report job tracker failure on hod client side when job tracker fails to come up In-Reply-To: <104022927.1213194525004.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ 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.