You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Robert Nettleton (JIRA)" <ji...@apache.org> on 2014/10/29 17:26:35 UTC
[jira] [Created] (AMBARI-8021) Hostname information included in
Blueprint export for HDP 2.2 cluster
Robert Nettleton created AMBARI-8021:
----------------------------------------
Summary: Hostname information included in Blueprint export for HDP 2.2 cluster
Key: AMBARI-8021
URL: https://issues.apache.org/jira/browse/AMBARI-8021
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 1.7.0
Reporter: Robert Nettleton
Assignee: Robert Nettleton
Fix For: 1.7.0
After launching an HDP 2.2 cluster using the Ambari UI, a Blueprint exported from the cluster will include hostname information for the following properties:
1. Hostname info appears after security is enabled (Knox also deployed in cluster):
core-site : "hadoop.proxyuser.knox.hosts"
webhcat-site: "webhcat.proxyuser.knox.hosts"
oozie-site: "hadoop.proxyuser.knox.hosts"
2. kafka-broker: "kafka.ganglia.metrics.host"
3. yarn-site: "hadoop.registry.zk.quorum"
slider-client: "slider.zookeeper.quorum"
kafka-broker: "zookeeper.connect"
The Knox-related properties only appear in the exported Blueprint when Knox and Security are enabled, but the other properties appear when the various services are deployed in either case (Slider, Kafka, Yarn).
The Blueprint configuration processor needs to be updated to account for these new properties in the HDP 2.2 stack.
I'm working on a patch for this, and will be submitting it shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)