[
https://issues.apache.org/jira/browse/AMBARI-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039162#comment-14039162
]
Erin A Boyd commented on AMBARI-6086:
-------------------------------------
[~u39kun] in AMBARI-4447 [~jaimin] enabled the ability for globals to be
defined for multiple services (as we did with the hadoop_heapsize for HDFS &
GlusterFS) So, why can we not do the same with the namenode_heapsize? If it's
defined in the global props with the service being GLUSTERFS, I don't
understand how it breaks HDFS.
We are having multiple issues with various services not starting up (Nagios,
HBASE, because of these global paratemeters not being defined). The error
looking like this (configuration parameters vary)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/NAGIOS/package/scripts/params.py",
line 137, in <module>
nn_ha_host_port_map[config['clusterHostInfo']['namenode_host'][0]] =
namenode_metadata_port
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
line 75, in __getattr__
raise Fail("Configuration parameter '"+self.name+"' was not found in
configurations dictionary!")
Fail: Configuration parameter 'namenode_host' was not found in configurations
dictionary!
Please advise...
> Add Gluster 2.1 Support for HDP
> -------------------------------
>
> Key: AMBARI-6086
> URL: https://issues.apache.org/jira/browse/AMBARI-6086
> Project: Ambari
> Issue Type: New Feature
> Components: build
> Affects Versions: 1.6.1
> Reporter: Scott Creeley
> Assignee: Scott Creeley
> Labels: 2.1.GlusterFS
> Fix For: 1.6.1
>
> Attachments: AMBARI-6086.patch, AMBARI-6086TRUNK.patch,
> AMBARI-TRUNK-2.patch
>
>
> Implement 2.1.GlusterFS stack for version 1.6.1 and above.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
