ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrii Tkach (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-3839) DataNode heapsize config override causes DataNode to not start
Date Thu, 21 Nov 2013 11:04:57 GMT
Andrii Tkach created AMBARI-3839:
------------------------------------

             Summary: 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


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)

Mime
View raw message