[
https://issues.apache.org/jira/browse/AMBARI-23397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23397:
------------------------------------
Labels: pull-request-available (was: )
> Blueprint deployments for NameNode Federation Fail
> --------------------------------------------------
>
> Key: AMBARI-23397
> URL: https://issues.apache.org/jira/browse/AMBARI-23397
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
> Affects Versions: 2.7.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> Ambari 2.7.0 will include support for HDFS NameNode Federation deployments,
> as detailed in:
> AMBARI-22916
> Blueprint deployments that attempt to use NameNode Federation currently fail
> with the following exception:
>
> {code:java}
> {u'status': 400, u'message': u'Topology validation failed:
> org.apache.ambari.server.topology.InvalidTopologyException: NAMENODE HA
> requires exactly 2 hosts running NAMENODE but there are: 4 Hosts:
> [ctr-e138-1518143905142-139109-01-000005.hwx.site,
> ctr-e138-1518143905142-139109-01-000006.hwx.site,
> ctr-e138-1518143905142-139109-01-000003.hwx.site,
> ctr-e138-1518143905142-139109-01-000004.hwx.site]'}{code}
>
> The Blueprint configuration processor needs to be updated in order to
> properly handle HDFS HA deployments that include Federated nameservices.
> This will generally mean that HA deployments can now support more than 2
> NameNode instances.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
