hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3954) Clean up passing HEAPSIZE to yarn and mapred commands.
Date Mon, 05 Mar 2012 19:00:02 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222508#comment-13222508
] 

Vinod Kumar Vavilapalli commented on MAPREDUCE-3954:
----------------------------------------------------

bq.  The test failures are unrelated, we have to investigate separately.
Figured this as a Jenkins issue. Happens intermittently, perhaps because of some permissions
issues.
                
> Clean up passing HEAPSIZE to yarn and mapred commands.
> ------------------------------------------------------
>
>                 Key: MAPREDUCE-3954
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3954
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.2
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>            Priority: Blocker
>         Attachments: MAPREDUCE-3954-20120305.txt, MR-3954.txt, MR-3954.txt, MR-3954.txt
>
>
> Currently the heap size for all of these is set in yarn-env.sh.  JAVA_HEAP_MAX is set
to -Xmx1000m unless YARN_HEAPSIZE is set.  If it is set it will override JAVA_HEAP_MAX.  However,
we do not always want to have the RM, NM, and HistoryServer with the exact same heap size.
 It would be logical to have inside of yarn and mapred to set JAVA_HEAP_MAX if YARN_RESOURCEMANAGER_HEAPSIZE,
YARN_NODEMANAGER_HEAPSIZE or HADOOP_JOB_HISTORYSERVER_HEAPSIZE are set respectively.  This
is a bug because it is easy to configure the history server to store more entires then the
heap can hold.  It is also a performance issue if we do not allow the history server to cache
many entries on a large cluster.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message