[
https://issues.apache.org/jira/browse/AMBARI-12214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608220#comment-14608220
]
Tom Beerbower commented on AMBARI-12214:
----------------------------------------
Pushed into trunk and branch-2.1 ...
commit df9c510732a8dab6bfc14936e0241683f5b0eb4e
Author: tbeerbower <[email protected]>
Date: Tue Jun 30 08:35:14 2015 -0400
AMBARI-12214 - Default ATLAS JVM options getting overwritten by empty space
when deployed via Ambari (Jonathan Maron via tbeerbower)
commit ac6e99ee573bd8eded77cefe00836fe63fdd63bc
Author: tbeerbower <[email protected]>
Date: Tue Jun 30 08:35:14 2015 -0400
AMBARI-12214 - Default ATLAS JVM options getting overwritten by empty space
when deployed via Ambari (Jonathan Maron via tbeerbower)
> Default ATLAS JVM options getting overwritten by empty space when deployed
> via Ambari
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-12214
> URL: https://issues.apache.org/jira/browse/AMBARI-12214
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.1.0
> Reporter: Jonathan Maron
> Assignee: Jonathan Maron
> Priority: Critical
> Fix For: 2.1.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Currently the atlas jvm options in the the atlas-env config file is set to an
> empty space. It appears that ambari doesn't treat that as a null value but
> rather as a space, so the space ends up overwriting the -Xmx1024m setting
> that is the default option for atlas start script. In order to stay
> consistent the default value of the jmv options in ambari will be modified
> from the space to the same value as the native scripts (-Xmx1024m).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
