Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 24 Apr 2012 05:08:35 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <211969145.8047.1335244115058.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <813719240.8019.1335243156014.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-3315) Improve bootstrapStandby error
 message when other NN has misconfigured http address
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260224#comment-13260224 ] 

Aaron T. Myers commented on HDFS-3315:
--------------------------------------

Another thing we could do would be to see if the HTTP/S address we determine for the other NN is the same as the HTTP/S address for _this_ NN. I suspect that would catch the most common case.
                
> Improve bootstrapStandby error message when other NN has misconfigured http address
> -----------------------------------------------------------------------------------
>
>                 Key: HDFS-3315
>                 URL: https://issues.apache.org/jira/browse/HDFS-3315
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: ha
>    Affects Versions: 2.0.0
>            Reporter: Todd Lipcon
>            Priority: Minor
>
> Currently, if the user forgets to configure the HTTP server address distinctly for each NN, bootstrapStandby emits and ugly stack trace with little indication as to which config is the issue. We should catch the exception and display a more actionable error message.

--
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