hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10950) rework heap management vars
Date Fri, 08 Aug 2014 19:11:12 GMT

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

Allen Wittenauer commented on HADOOP-10950:
-------------------------------------------

Proposal:

* Introduce HADOOP_HEAPSIZE_MAX and HADOOP_HEAPSIZE_MIN, both default to empty. They will
set the Xmx and Xms values, respectively. Both require units to be provided, such that e.g.
HADOOP_HEAPSIZE_MAX="10g" is valid.  This will allow for JVM autoscaling for those users who
want it (the real intent of the highly flawed HADOOP-10759 "patch").
* Deprecate HADOOP_HEAPSIZE.   Remove JAVA_HEAP MAX.  Completely remove them from the hadoop-env.sh,
etc. documentation. The code should honor HADOOP_HEAPSIZE if set (thereby providing backwards
compatibility), but the HADOOP_HEAPSIZE_xyz vars take precedence in case of a conflict.


> rework  heap management  vars
> -----------------------------
>
>                 Key: HADOOP-10950
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10950
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Allen Wittenauer
>
> Post-HADOOP-9902, we need to rework how heap is configured for small footprint machines,
deprecate some options, introduce new ones for greater flexibility.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message