[
https://issues.apache.org/jira/browse/AMBARI-10411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Nettleton updated AMBARI-10411:
--------------------------------------
Attachment: AMBARI-10411.patch
Upload of initial patch to address this issue.
> Yarn ResourceManager HA config properties not processed properly by Blueprints
> ------------------------------------------------------------------------------
>
> Key: AMBARI-10411
> URL: https://issues.apache.org/jira/browse/AMBARI-10411
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-10411.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> In order to reproduce this problem:
> 1. Use the Ambari UI to deploy a multi-node Yarn cluster
> 2. Use the Ambari UI wizard to enable Yarn ResourceManager High-Availability
> 3. Use the Ambari REST API to request an exported Blueprint based on the
> running cluster.
> When exporting a Blueprint from a running cluster that utilizes Yarn
> ResourceManager High-Availability (HA), the following Yarn configuration
> properties (HA-related) are not properly exported, and hostname information
> is included in the exported Blueprint.
> The following properties are not exported properly:
> yarn.resourcemanager.hostname.$NAME_OF_RM
> Note: $NAME_OF_RM indicates the name of a running resource manager in Yarn.
> In an HA deployment scenario, this property name will include the name of a
> resource manager, and will point towards the host that this resource manager
> is deployed on. There will be one instance of this property per resource
> manager. For most scenarios, this means there will be at most 2 of these
> properties to consider.
> yarn.resourcemanager.zk-address
> Note: This property should refer to a comma-separate list of Zookeeper
> servers.
> In each of these cases, the Blueprint configuration processor should strip
> out the hostname information, and substitute the name of the host group that
> includes this host service.
> These changes should be implemented in the BlueprintConfigurationProcessor
> class.
> This bug will not keep a Yarn HA Blueprint from deploying, but will affect
> the round-tripping process of deploying a new cluster based on a Blueprint,
> since the hostname information would need to be manually updated if the host
> names have changed for the cluster deployment.
> This bug will also affect the usage of %HOSTGROUP% syntax in Yarn HA
> properties, since the config processor is not properly handling the export of
> these properties from a running cluster, nor is is properly handling
> subsitution at cluster deployment time for Yarn HA properties.
> AMBARI-10524 also reports that the following Yarn properties are not properly
> exported:
> "yarn.resourcemanager.webapp.https.address" and
> "yarn.resourcemanager.zk-address"
> Work on this bug should also verify that all Yarn properties with hostnames
> are properly exported, meaning that no hostnames should be included in the
> exported Blueprint.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
