Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 90128 invoked from network); 17 Jun 2008 08:16:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Jun 2008 08:16:43 -0000 Received: (qmail 66560 invoked by uid 500); 17 Jun 2008 08:16:38 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 66527 invoked by uid 500); 17 Jun 2008 08:16:38 -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 66516 invoked by uid 99); 17 Jun 2008 08:16:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jun 2008 01:16:38 -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; Tue, 17 Jun 2008 08:15:56 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 45478234C145 for ; Tue, 17 Jun 2008 01:15:45 -0700 (PDT) Message-ID: <808058611.1213690545282.JavaMail.jira@brutus> Date: Tue, 17 Jun 2008 01:15:45 -0700 (PDT) From: "Devaraj Das (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Updated: (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:all-tabpanel ] Devaraj Das updated HADOOP-3531: -------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) I just committed this. Thanks, Hemanth! > 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.