[jira] [Commented] (HDFS-5227) Namenode.getAddress() should return namenode rpc-address

2013-09-19 Thread Chuan Liu (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772293#comment-13772293
 ] 

Chuan Liu commented on HDFS-5227:
-

bq. -1 core tests. The patch failed these unit tests in 
hadoop-hdfs-project/hadoop-hdfs:
I will take a look at the failures.


 Namenode.getAddress() should return namenode rpc-address
 

 Key: HDFS-5227
 URL: https://issues.apache.org/jira/browse/HDFS-5227
 Project: Hadoop HDFS
  Issue Type: Bug
Affects Versions: 3.0.0, 2.1.1-beta
Reporter: Chuan Liu
Assignee: Chuan Liu
 Attachments: HDFS-5227-trunk.patch


 Currently, {{Namenode.getAddress(Configuration conf)}} will return default 
 file system address as its result. The correct behavior should be returning 
 config value of dfs.namenode.rpc-address if it presents in the 
 configurations. Otherwise namenode will fail to start if the default file 
 system is configured to another file system other than the one running in the 
 cluster. We have a similar issue in 1.0 code base. The JIRA is HDFS-4320. The 
 previous JIRA is closed and we cannot open it. Thus create a new one to track 
 the issue in trunk.

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


[jira] [Commented] (HDFS-5227) Namenode.getAddress() should return namenode rpc-address

2013-09-18 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HDFS-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771486#comment-13771486
 ] 

Hadoop QA commented on HDFS-5227:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12603934/HDFS-5227-trunk.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-hdfs-project/hadoop-hdfs:

  org.apache.hadoop.hdfs.server.datanode.TestDeleteBlockPool
  org.apache.hadoop.hdfs.TestDFSShell
  
org.apache.hadoop.hdfs.server.balancer.TestBalancerWithNodeGroup

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/4999//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4999//console

This message is automatically generated.

 Namenode.getAddress() should return namenode rpc-address
 

 Key: HDFS-5227
 URL: https://issues.apache.org/jira/browse/HDFS-5227
 Project: Hadoop HDFS
  Issue Type: Bug
Affects Versions: 3.0.0, 2.1.1-beta
Reporter: Chuan Liu
Assignee: Chuan Liu
 Attachments: HDFS-5227-trunk.patch


 Currently, {{Namenode.getAddress(Configuration conf)}} will return default 
 file system address as its result. The correct behavior should be returning 
 config value of dfs.namenode.rpc-address if it presents in the 
 configurations. Otherwise namenode will fail to start if the default file 
 system is configured to another file system other than the one running in the 
 cluster. We have a similar issue in 1.0 code base. The JIRA is HDFS-4320. The 
 previous JIRA is closed and we cannot open it. Thus create a new one to track 
 the issue in trunk.

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