[
https://issues.apache.org/jira/browse/AMBARI-4933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577289#comment-14577289
]
Andrew Onischuk commented on AMBARI-4933:
-----------------------------------------
+
oozie_heapsize
oozie_permsize
> Some default stack configuration values need to have "m" appended to them
> -------------------------------------------------------------------------
>
> Key: AMBARI-4933
> URL: https://issues.apache.org/jira/browse/AMBARI-4933
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 1.5.0
> Reporter: John Speidel
>
> Some of the default configurations values which are included in the various
> stack definitions need to have "m" appended to them to be valid values.
> Currently, the UI appends the "m" to the value prior to cluster configuration.
> This is a problem going forward as the stack definition is meant to be a self
> contained representation of the stack version. Because of this issue,
> Blueprints and any api clients, including Openstack Savanna need to have hard
> coded knowledge to append "m" to certain configuration property values.
> This change will need to be coordinated with the UI and now Blueprints as
> both are appending "m" to the configuration values.
> Offending properties are:
> namenode_heapsize
> namenode_opt_newsize
> namenode_opt_maxnewsize
> dtnode_heapsize
> jtnode_opt_newsize
> jtnode_opt_maxnewsize
> jtnode_heapsize
> hbase_master_heapsize
> hbase_regionserver_heapsize
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
