[
https://issues.apache.org/jira/browse/AMBARI-23434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423989#comment-16423989
]
Hudson commented on AMBARI-23434:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8967 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8967/])
AMBARI-23434. Fix stack issues in HDFS to support Namenode Federation
(aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=0824ed2c7b8699f561ff18ce0d5c4508cfe65791])
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
* (edit) ambari-common/src/main/python/resource_management/core/shell.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/namenode_ha_utils.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/providers/hdfs_resource.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* (edit)
ambari-common/src/main/python/resource_management/core/providers/system.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/zkfc_slave.py
* (edit)
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
> Fix stack issues in HDFS to support Namenode Federation setup
> -------------------------------------------------------------
>
> Key: AMBARI-23434
> URL: https://issues.apache.org/jira/browse/AMBARI-23434
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: AMBARI-23434.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> For example, here are 2 things I found to be probably wrong.
> 1\. Journal node restart failed because we cannot find hdfs-site :
> dfs.journalnode.edits.dir. We delete that property in the wizard. We may have
> to change that to dfs.journalnode.edits.dir.<nameservice>
> 2\. The following snippet in params_linux.py on HDFS 3.0 stack seems wrong. It
> has been designed to work with only 1 nameservice.
>
>
>
> dfs_ha_enabled = False
> dfs_ha_nameservices =
> default('/configurations/hdfs-site/dfs.internal.nameservices', None)
> if dfs_ha_nameservices is None:
> dfs_ha_nameservices =
> default('/configurations/hdfs-site/dfs.nameservices', None)
> dfs_ha_namenode_ids =
> default(format("/configurations/hdfs-site/dfs.ha.namenodes.{dfs_ha_nameservices}"),
> None)
>
> 3\. After setting up NN Fed, when I restart namenodes, I see the following
> error.
>
>
>
> main_resource.resource.security_enabled,
> main_resource.resource.logoutput)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 154, in __init__
> security_enabled, run_user)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/namenode_ha_utils.py",
> line 204, in get_property_for_active_namenode
> if INADDR_ANY in value and rpc_key in hdfs_site:
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found
> in configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'dfs.namenode.https-address.ns2.nn1' was not found in configurations
> dictionary!
>
> This is probably because the namenode_ha_utils is not equipped to handle
> multiple nameservices.
> We may have to create to fix such stack errors when the wizard is done.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
