Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <309503.54461280352976276.JavaMail.jira@thor>
Date: Wed, 28 Jul 2010 17:36:16 -0400 (EDT)
From: "gary murry (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.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.
In-Reply-To: <21649469.54401280352736640.JavaMail.jira@thor>
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 ]

gary murry updated HDFS-1321:
-----------------------------

    Priority: Minor  (was: Major)

> 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
>            Reporter: gary murry
>            Priority: Minor
>
> 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.
-
You can reply to this email to add a comment to the issue online.