[
https://issues.apache.org/jira/browse/HDFS-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901600#comment-14901600
]
Anu Engineer commented on HDFS-9112:
------------------------------------
[~jingzhao] Thanks for the pointer to the [~dlmarion] 's comments. I see that
we had assumed that it is better to let users specify -ns option if they have
this kind of HA setup. However it looks like both us and cloudera ran into this
issue in the field hence I think we need to have a little more clarity with
error messages, with the current code the error message is very cryptic.
{code}
hdfs haadmin -getServiceState nn2
Illegal argument: Unable to determine the nameservice id.
{code}
This gives no clue to the user that they are expected to specify -ns option.
Also from the comments that you pointed me to I am not able to decipher why it
is better to specify "-ns" by the user, when we have that information in the
config files. Since I don't have much context on HDFS-6376, I would appreciate
if you can provide some rationale (From cursory comment reading it looks to me
that Dave originally had exclude settings which created some issues, but
[~wheat9] modified them to internal nameservices. If so using internal name
services hopefully should not cause a failure.)
if you like I can modify this patch to print out an error message which asks
user to add -ns option explicitly, instead of reading the name services name
from config, that would be a trivial change. Please let me know if you think I
should do that or if this change looks good enough.
> 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)
