You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2014/04/24 15:36:31 UTC
[jira] [Resolved] (AMBARI-5485) Ambari should Manage JobHistory
Heap Size
[ https://issues.apache.org/jira/browse/AMBARI-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Onischuk resolved AMBARI-5485.
-------------------------------------
Resolution: Fixed
Committed to trunk
> Ambari should Manage JobHistory Heap Size
> -----------------------------------------
>
> Key: AMBARI-5485
> URL: https://issues.apache.org/jira/browse/AMBARI-5485
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 1.6.0
>
>
> PROBLEM: Ambari does not manage mapred-env.sh and JobHistory memory cannot be
> set via Ambari.
> BUSINESS IMPACT: Users are not sure how to change JobHistory memory settings
> in Ambari cluster. This came from eBay so looks like large clusters need to be
> able to increase memory.
> STEPS TO REPRODUCE: navigate to Services -> Mapreduce -> Configs tab and you
> will notice that JobHistory Heap configuration is not there.
> ACTUAL BEHAVIOR: Cannot change JobHistory memory in Ambari UI
> EXPECTED BEHAVIOR: To be able to manage JobHistory memory in Ambari UI
> SUPPORT ANALYSIS: Since Ambari does not manage mapred-env.sh you can manually
> edit config in mapred-env.sh. I verified by manually setting the memory and
> restarting cluster via Ambari that config value did not change.
>
>
>
> [root@63ambarihdp2010 conf]# grep -i heap /etc/hadoop/conf/mapred-env.sh
> export HADOOP_JOB_HISTORYSERVER_HEAPSIZE=900
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)