[
https://issues.apache.org/jira/browse/HDFS-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901613#comment-14901613
]
Jing Zhao commented on HDFS-9112:
---------------------------------
Thanks for the clarification, [~anu]! I think for admin or other clients it's
not necessary for them to clearly distinguish internal/external name services.
The internal/external ns makes sense maybe only to DataNodes. Thus I'm
currently leaning towards requiring admins to explicitly specify the name
service using "-ns" option. But I completely agree with you that we should
improve the error message.
> Haadmin fails if multiple name service IDs are configured
> ---------------------------------------------------------
>
> Key: HDFS-9112
> URL: https://issues.apache.org/jira/browse/HDFS-9112
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: tools
> Affects Versions: 2.7.1
> Reporter: Anu Engineer
> Assignee: Anu Engineer
> Attachments: HDFS-9112.001.patch
>
>
> In HDFS-6376 we supported a feature for distcp that allows multiple
> NameService IDs to be specified so that we can copy from two HA enabled
> clusters.
> That confuses haadmin command since we have a check in
> DFSUtil#getNamenodeServiceAddr which fails if it finds more than 1 name in
> that property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
