You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Ajith S (JIRA)" <ji...@apache.org> on 2015/04/06 14:34:13 UTC
[jira] [Commented] (HDFS-8067) haadmin commands doesn't work in
Federation with HA
[ https://issues.apache.org/jira/browse/HDFS-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481175#comment-14481175 ]
Ajith S commented on HDFS-8067:
-------------------------------
After analysis i found that the cause is
{code:title=NNHAServiceTarget.java|borderStyle=solid}
public NNHAServiceTarget(Configuration conf,
String nsId, String nnId) {
Preconditions.checkNotNull(nnId);
if (nsId == null) {
nsId = DFSUtil.getOnlyNameServiceIdOrNull(conf);
if (nsId == null) {
throw new IllegalArgumentException(
"Unable to determine the nameservice id.");
}
}
......
{code}
Here, by using {code:} getOnlyNameServiceIdOrNull(conf) {code} to determine the nameserviceID, when configured in a Federated setup which has multiple nameservices, returns null. This was updated as part of HDFS-3084
I am thinking to change it to {code:} getNamenodeNameServiceId(conf) {code}
Please suggest
> haadmin commands doesn't work in Federation with HA
> ---------------------------------------------------
>
> Key: HDFS-8067
> URL: https://issues.apache.org/jira/browse/HDFS-8067
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Ajith S
> Assignee: Ajith S
>
> Scenario : Setting up multiple nameservices with HA configuration for each nameservice (manual failover)
> After starting the journal nodes and namenodes, both the nodes are in standby mode.
> all the following haadmin commands
> *haadmin*
> -transitionToActive
> -transitionToStandby
> -failover
> -getServiceState
> -checkHealth
> failed with exception
> _Illegal argument: Unable to determine the nameservice id._
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)