[jira] [Resolved] (HDFS-3439) Balancer exits if fs.defaultFS is set to a different, but semantically identical, URI from dfs.namenode.rpc-address

["Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org>]

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

Tsz Wo Nicholas Sze resolved HDFS-3439.
---------------------------------------
          Resolution: Cannot Reproduce
    Target Version/s:   (was: )

Resolving as Cannot Reproduce.
{code}
$hadoop balancer -Dfs.defaultFS=hdfs://foo.example.com:8020/ -Ddfs.namenode.servicerpc-address=hdfs://foo.example.com:8020
DEPRECATED: Use of this script to execute hdfs command is deprecated.
Instead use the hdfs command for it.

15/12/03 13:47:12 INFO balancer.Balancer: namenodes  = [hdfs://foo.example.com:8020]
{code}

> Balancer exits if fs.defaultFS is set to a different, but semantically identical, URI from dfs.namenode.rpc-address
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3439
>                 URL: https://issues.apache.org/jira/browse/HDFS-3439
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: balancer & mover
>    Affects Versions: 2.0.0-alpha
>            Reporter: Aaron T. Myers
>
> The balancer determines the set of NN URIs to balance by looking at fs.defaultFS and all possible dfs.namenode.(service)rpc-address settings. If fs.defaultFS is, for example, set to "hdfs://foo.example.com:8020/" (note the trailing "/") and the rpc-address is set to "hdfs://foo.example.com:8020" (without a "/"), then the balancer will conclude that there are two NNs and try to balance both. However, since both of these URIs refer to the same actual FS instance, the balancer will exit with "java.io.IOException: Another balancer is running.  Exiting ..."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)