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 04D8FE17E for ; Tue, 19 Feb 2013 10:01:16 +0000 (UTC) Received: (qmail 59385 invoked by uid 500); 19 Feb 2013 10:01:15 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 59067 invoked by uid 500); 19 Feb 2013 10:01:15 -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 59012 invoked by uid 99); 19 Feb 2013 10:01:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Feb 2013 10:01:14 +0000 Date: Tue, 19 Feb 2013 10:01:14 +0000 (UTC) From: "Harsh J (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-3447) StandbyException should not be logged at ERROR level on server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581172#comment-13581172 ] Harsh J commented on HDFS-3447: ------------------------------- I agree, DEBUG would be good. When needed, it can be enabled specifically via the /logLevel too (by setting the appropriate class). > StandbyException should not be logged at ERROR level on server > -------------------------------------------------------------- > > Key: HDFS-3447 > URL: https://issues.apache.org/jira/browse/HDFS-3447 > Project: Hadoop HDFS > Issue Type: Improvement > Components: ha > Affects Versions: 2.0.0-alpha > Reporter: Todd Lipcon > Assignee: Robert Justice > Priority: Minor > Labels: newbie > > Currently, the standby NN will log StandbyExceptions at ERROR level any time a client tries to connect to it. So, if the second NN in an HA pair is active, the first NN will spew a lot of these errors in the log, as each client gets redirected to the proper NN. Instead, this should be at INFO level, and should probably be logged in a less "scary" manner (eg "Received READ request from client 1.2.3.4, but in Standby state. Redirecting client to other NameNode.") -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira