[
https://issues.apache.org/jira/browse/HDFS-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697715#comment-13697715
]
Uma Maheswara Rao G commented on HDFS-4837:
-------------------------------------------
Whether this is working with HA namenodes? if nameServiceAddress available,
directly it will create connection right? Otherwise anyway this looks to be
same as FileSystem.getDefaultUri(conf) and create address. I think having
default behaviour only more correct I feel, As your installation default FS
says something else. So, if you want to pass uri explicitely also, you can pass
your specific configurations via command line. This is service address used by
DN, backup node...etc. Could you please have a test with HA namenodes and
confirm befor providing revised patch? ALso take care of calling getDFS in
setBalancerBandwidth instead of getFS.
Regards,
Uma
> Allow DFSAdmin to run when HDFS is not the default file system
> --------------------------------------------------------------
>
> Key: HDFS-4837
> URL: https://issues.apache.org/jira/browse/HDFS-4837
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Mostafa Elhemali
> Assignee: Mostafa Elhemali
> Attachments: HDFS-4837.patch
>
>
> When Hadoop is running a different default file system than HDFS, but still
> have HDFS namenode running, we are unable to run dfsadmin commands.
> I suggest that DFSAdmin use the same mechanism as NameNode does today to get
> its address: look at dfs.namenode.rpc-address, and if not set fallback on
> getting it from the default file system.
--
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
