You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Balázs Bence Sári (JIRA)" <ji...@apache.org> on 2016/05/23 16:57:12 UTC
[jira] [Resolved] (AMBARI-16823) Hostname substitutions for
Namenode HA Initial State properties does not work
[ https://issues.apache.org/jira/browse/AMBARI-16823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Balázs Bence Sári resolved AMBARI-16823.
----------------------------------------
Resolution: Duplicate
> Hostname substitutions for Namenode HA Initial State properties does not work
> -----------------------------------------------------------------------------
>
> Key: AMBARI-16823
> URL: https://issues.apache.org/jira/browse/AMBARI-16823
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Balázs Bence Sári
> Assignee: Balázs Bence Sári
> Fix For: 2.4.0
>
>
> {code}
> {
> "hadoop-env": {
> "properties" : {
> "dfs_ha_initial_namenode_active" : "%HOSTGROUP::master_1%",
> "dfs_ha_initial_namenode_standby" : "%HOSTGROUP::master_2%"
> }}
> }
> {code}
> When these properties are included in the blueprint during HA blueprint deployment hostname substitutions do not work. Other properties in the blueprint get substituted correctly.
> Talked to [~rnettleton] about the issue and he verified that this is an issue in BlueprintConfigurationProcessor
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)