THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Code Block | ||||
---|---|---|---|---|
| ||||
... <provider> <role>ha</role> <name>HaProvider</name> <enabled>true</enabled> <param> <name>WEBHDFS</name> <value>maxFailoverAttempts=3;failoverSleep=1000;maxRetryAttempts=300;retrySleep=1000;enabled=true</value> </param> <param> <name>HIVE</name> <value>maxFailoverAttempts=3;failoverSleep=1000;enabled=true;zookeeperEnsemble=c6801.ambari.apache.orghost1:2181,c6802.ambari.apache.orghost2:2181,c6803.ambari.apache.orghost3:2181;zookeeperNamespace=hiveserver2</value> </param> </provider> </gateway> <service> <role>WEBHDFS</role> <url>http://c6801.ambari.apache.org:50070/webhdfs</url> <url>http://c6802.ambari.apache.org:50070/webhdfs</url> </service> <service> <role>HIVE</role> </service> ... |
...
Service Config | Property | Example Value |
---|---|---|
hive-site | hive.zookeeper.quorum | c6801.ambari.apache.orghost1:2181,c6802.ambari.apache.orghost2:2181,c6803.ambari.apache.orghost3:2181 |
hive.server2.zookeeper.namespace | hiveserver2 | |
hive.server2.support.dynamic.service.discovery | true | |
hbase-site | hbase.zookeeper.quorum | c6801.ambari.apache.orghost1:2181,c6802.ambari.apache.orghost2:2181,c6803.ambari.apache.orghost3:2181 |
zookeeper.znode.parent | /hbase-unsecure | |
kafka-broker | zookeeper.connect | sandbox.hortonworks.com:2181 |
hdfs-site | ha.zookeeper.quorum | c6801.ambari.apache.orghost1:2181,c6802.ambari.apache.orghost2:2181,c6803.ambari.apache.orghost3:2181 |
dfs.ha.automatic-failover.enabled | true (only for "Auto HA") | |
oozie-site | oozie.zookeeper.connection.string | localhost:2181 |
oozie.zookeeper.namespace | oozie | |
yarn-site |
| true |
| c6801.ambari.apache.orghost1:2181,c6802.ambari.apache.orghost2:2181,c6803.ambari.apache.orghost3:2181 | |
webhcat-site | templeton.zookeeper.hosts | c6801.ambari.apache.orghost1:2181,c6802.ambari.apache.orghost2:2181,c6803.ambari.apache.orghost3:2181 |
Required Changes
- Knox will parse referenced provider configurations, rather than just blindly copying their contents.
This will serve multiple purposes:- It will provide a degree of validation (invalid provider configurations would fail parsing)
- It will allow a finer level of control over what is serialized to the generated topology file:
- Knox will have the opportunity to add cluster-specific details into provider configuration in the generated topologies
- Knox could reference elements of the provider configuration (e.g., HaProvider) to inform the generation of service elements in the generated topologies.
...