You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2013/12/27 18:05:52 UTC
[jira] [Updated] (AMBARI-4189) 'DataNode maximum Java heap size'
and 'Hadoop maximum Java heap size' overrides for config groups didn't get
persisted during installer
[ https://issues.apache.org/jira/browse/AMBARI-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonenko Alexander updated AMBARI-4189:
----------------------------------------
Description:
1. During hadoop installation 2 config groups were created for HDFS with overrides for properties as in *hdfsInstaller.png*.
2. After hadoop installation the config tab of Hdfs looks like *hdfsInMonitoring.png*
Checked that 2 other properties 'DataNode directories' and 'Reserved space for HDFS' were persisted correctly for both config groups.
But the 'DataNode maximum Java heap size' and 'Hadoop maximum Java heap size' have the same default values in /etc/hadoop/conf/hadoop-env.sh:
{noformat}
export HADOOP_HEAPSIZE="1024"
...
HADOOP_DATANODE_OPTS="-Xmx1024m -Dhadoop.security.logger=ERROR,DRFAS ${HADOOP_DATANODE_OPTS}"
{noformat}
was:
On the following cluster:
172.18.145.209
172.18.145.184
172.18.145.161
172.18.145.72
172.18.145.165
172.18.145.213
cv-try-1-11.cs1cloud.internal - 2-ond config-group
cv-try-1-10.cs1cloud.internal - 1-st config-group
cv-try-1-6.cs1cloud.internal - 1-st config-group
cv-try-1-2.cs1cloud.internal- 2-ond config-group
cv-try-1-7.cs1cloud.internal- 2-ond config-group
cv-try-1-12.cs1cloud.internal- 2-ond config-group
PUBLIC GATEWAY -> http://172.18.145.209:8080/
1. During hadoop installation 2 config groups were created for HDFS with overrides for properties as in *hdfsInstaller.png*.
2. After hadoop installation the config tab of Hdfs looks like *hdfsInMonitoring.png*
Checked that 2 other properties 'DataNode directories' and 'Reserved space for HDFS' were persisted correctly for both config groups.
But the 'DataNode maximum Java heap size' and 'Hadoop maximum Java heap size' have the same default values in /etc/hadoop/conf/hadoop-env.sh:
{noformat}
export HADOOP_HEAPSIZE="1024"
...
HADOOP_DATANODE_OPTS="-Xmx1024m -Dhadoop.security.logger=ERROR,DRFAS ${HADOOP_DATANODE_OPTS}"
{noformat}
> 'DataNode maximum Java heap size' and 'Hadoop maximum Java heap size' overrides for config groups didn't get persisted during installer
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-4189
> URL: https://issues.apache.org/jira/browse/AMBARI-4189
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.3
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 1.4.3
>
>
> 1. During hadoop installation 2 config groups were created for HDFS with overrides for properties as in *hdfsInstaller.png*.
> 2. After hadoop installation the config tab of Hdfs looks like *hdfsInMonitoring.png*
> Checked that 2 other properties 'DataNode directories' and 'Reserved space for HDFS' were persisted correctly for both config groups.
> But the 'DataNode maximum Java heap size' and 'Hadoop maximum Java heap size' have the same default values in /etc/hadoop/conf/hadoop-env.sh:
> {noformat}
> export HADOOP_HEAPSIZE="1024"
> ...
> HADOOP_DATANODE_OPTS="-Xmx1024m -Dhadoop.security.logger=ERROR,DRFAS ${HADOOP_DATANODE_OPTS}"
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)