[
https://issues.apache.org/jira/browse/AMBARI-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828834#comment-13828834
]
Aleksandr Kovalenko commented on AMBARI-3839:
---------------------------------------------
+1 for the patch
> DataNode heapsize config override causes DataNode to not start
> --------------------------------------------------------------
>
> Key: AMBARI-3839
> URL: https://issues.apache.org/jira/browse/AMBARI-3839
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.3
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 1.4.3
>
> Attachments: AMBARI-3839.patch
>
>
> On the Default config group I changed the {{DataNode maximum Java heap size}}
> property to 1000 and saved. In the API it correctly saved it as
> {{dtnode_heapsize: "1000m"}}.
> I then did something similar for a config-group - I overrode the value to be
> 1111. However in the API it got persisted without the "m" at end - so
> DataNode would not start.
> {code}
> {
> "href" :
> "http://server:8080/api/v1/clusters/c1/configurations?type=global&tag=version1384986866403";,
> "items" : [
> {
> "href" :
> "http://server:8080/api/v1/clusters/c1/configurations?type=global&tag=version1384986866403";,
> "tag" : "version1384986866403",
> "type" : "global",
> "Config" : {
> "cluster_name" : "c1"
> },
> "properties" : {
> "dtnode_heapsize" : "1111"
> }
> }
> ]
> }
> {code}
> We should make sure that all pre-save processing we do for Default configs
> happens for the overridden configs also.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
