Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3101597DE for ; Fri, 10 Feb 2012 04:17:31 +0000 (UTC) Received: (qmail 58754 invoked by uid 500); 10 Feb 2012 04:17:27 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 58517 invoked by uid 500); 10 Feb 2012 04:17:09 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 58496 invoked by uid 99); 10 Feb 2012 04:17:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2012 04:17:01 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2012 04:16:31 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id E8A0A1AEB00 for ; Fri, 10 Feb 2012 04:16:10 +0000 (UTC) Date: Fri, 10 Feb 2012 04:16:05 +0000 (UTC) From: "Uma Maheswara Rao G (Commented) (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1043698542.23005.1328847370955.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-776) Fix exception handling in Balancer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205213#comment-13205213 ] Uma Maheswara Rao G commented on HDFS-776: ------------------------------------------ Yep, considering multiple Namenodes support in Balancer today, your points make sense to me. {quote} How about throwing an exception in getAccessToken(..) when it is called? We may set shouldRun to false in run() and the check shouldRun in getAccessToken(..). {quote} this proposal sounds good. Let me take a look. > Fix exception handling in Balancer > ---------------------------------- > > Key: HDFS-776 > URL: https://issues.apache.org/jira/browse/HDFS-776 > Project: Hadoop HDFS > Issue Type: Bug > Components: balancer > Reporter: Owen O'Malley > Assignee: Uma Maheswara Rao G > Priority: Critical > Attachments: HDFS-776.0.patch, HDFS-776.patch, HDFS-776.patch > > > The Balancer's AccessKeyUpdater handles exceptions badly. In particular: > 1. Catching Exception too low. The wrapper around setKeys should only catch IOException. > 2. InterruptedException is ignored. It should be caught at the top level and exit run. > 3. Throwable is not caught. It should be caught at the top level and kill the Balancer server process. > {code} > class AccessKeyUpdater implements Runnable { > public void run() { > while (shouldRun) { > try { > accessTokenHandler.setKeys(namenode.getAccessKeys()); > } catch (Exception e) { > LOG.error(StringUtils.stringifyException(e)); > } > try { > Thread.sleep(keyUpdaterInterval); > } catch (InterruptedException ie) { > } > } > } > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira