You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "gary murry (JIRA)" <ji...@apache.org> on 2010/07/28 23:32:16 UTC

[jira] Created: (HDFS-1321) If service port and main port are the same, there is no clear log message explaining the issue.

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


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.

[jira] Updated: (HDFS-1321) If service port and main port are the same, there is no clear log message explaining the issue.

Posted by "gary murry (JIRA)" <ji...@apache.org>.

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