You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Attila Magyar (JIRA)" <ji...@apache.org> on 2017/07/11 13:27:00 UTC
[jira] [Updated] (AMBARI-21442) Ambari updates memory settings in
blueprint incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Attila Magyar updated AMBARI-21442:
-----------------------------------
Description:
Ambari appends a 'm' suffix to certain memory settings related properties during blueprint install.
For example if namenode_heapsize is 512 then Ambari will update it to 512m. However if the property already has a suffix like 4g then it will be updated to 4gm.
This patch does 2 things.
# Instead of the hardcoded 'm' suffix, it uses the stack defined unit.
# It check if the property already has some unit, and if that unit doesn't match the stack defined unit, then the blueprint will be rejected
was:
Ambari appends a 'm' suffix to certain memory settings related properties during blueprint install.
For example if namenode_heapsize is 512 them Ambari will update it to 512m. However if the property already has a suffix like 4g then it will be updated to 4gm.
This patch does 2 things.
# Instead of the hardcoded 'm' suffix, it uses the stack defined unit.
# It check if the property already has some unit, and if that unit doesn't match the stack defined unit, then the blueprint will be rejected
> Ambari updates memory settings in blueprint incorrectly
> -------------------------------------------------------
>
> Key: AMBARI-21442
> URL: https://issues.apache.org/jira/browse/AMBARI-21442
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.2
> Reporter: Attila Magyar
> Assignee: Attila Magyar
> Fix For: 3.0.0
>
>
> Ambari appends a 'm' suffix to certain memory settings related properties during blueprint install.
> For example if namenode_heapsize is 512 then Ambari will update it to 512m. However if the property already has a suffix like 4g then it will be updated to 4gm.
> This patch does 2 things.
> # Instead of the hardcoded 'm' suffix, it uses the stack defined unit.
> # It check if the property already has some unit, and if that unit doesn't match the stack defined unit, then the blueprint will be rejected
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)