Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 23 Jun 2011 17:47:47 +0000 (UTC)
From: "Jim Plush (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <2009382833.34062.1308851267424.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-1321) If service port and main port are the
 same, there is no clear log message explaining the issue.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Plush updated HDFS-1321:
----------------------------

    Attachment: HDFS-1321-take2.txt

did a hard reset and re-applied the changes to try and get a cleaner patch file

> If service port and main port are the same, there is no clear log message explaining the issue.
> -----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1321
>                 URL: https://issues.apache.org/jira/browse/HDFS-1321
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.23.0
>            Reporter: gary murry
>            Assignee: Jim Plush
>            Priority: Minor
>              Labels: newbie
>             Fix For: 0.23.0
>
>         Attachments: HDFS-1321-take2.txt, HDFS-1321.patch
>
>
> With the introduction of a service port to the namenode, there is now a chance for user error to set the two port equal.  This will cause the namenode to fail to start up.  It would be nice if there was a log message explaining the port clash.  Or just treat things as if the service port was not specified. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira