[
https://issues.apache.org/jira/browse/AMBARI-10487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Nettleton updated AMBARI-10487:
--------------------------------------
Attachment: AMBARI-10487.patch
Uploaded initial version of patch.
> Blueprint processor fails to handle direct host names properly in HA
> Blueprints
> -------------------------------------------------------------------------------
>
> Key: AMBARI-10487
> URL: https://issues.apache.org/jira/browse/AMBARI-10487
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-10487.patch,
> exported_ha_blueprint_with_manual_updates_direct_host_names.json,
> ha_cluster_creation_template.json
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> The Blueprint Configuration processor is not handling certain HA-specific
> properties (HDFS HA for one example) when host names are specified directly.
> If a customer wishes to specify hostnames directly in the HDFS HA properties
> that require hostnames, the Blueprint processor will fail if it detects more
> than one NameNode (which is the case in an HA cluster) and does not find the
> %HOSTGROUP% syntax to use for hostname substitution.
> The Blueprint config processor should be updated, so that customer-supplied
> hostnames in these properties are used, and the Blueprint processor should
> function properly with hostnames supplied directly.
> This fix should also be applied and tested across the other types of HA in
> Blueprints, and care should be taken to ensure that a customer can supply
> hostnames directly, or can use the %HOSTGROUP% syntax, or a combination of
> the two approaches.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
