[
https://issues.apache.org/jira/browse/HDFS-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901549#comment-14901549
]
Jing Zhao commented on HDFS-9112:
---------------------------------
We had a discussion in HDFS-6376 about this and [~dlmarion]'s point is it's
better to require admin to specify the name service id using "-ns" option in
haadmin commands in such a complex configuration scenario (please see his
comment
[here|https://issues.apache.org/jira/browse/HDFS-6376?focusedCommentId=14108157&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14108157]).
> 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)
