[ 
https://issues.apache.org/jira/browse/HADOOP-10950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Allen Wittenauer updated HADOOP-10950:
--------------------------------------
    Release Note: 
* HADOOP_HEAPSIZE variable has been deprecated  (It will still be honored if 
set, but expect it to go away in the future).    In its place, 
HADOOP_HEAPSIZE_MAX and HADOOP_HEAPSIZE_MIN have been introduced to set Xmx and 
Xms, respectively. 

* The internal variable JAVA_HEAP_MAX has been removed.

* Default heap sizes have been removed.  To re-enable the old default, 
configure HADOOP_HEAPSIZE_MAX="1g" in hadoop-env.sh. This will allow for the 
JVM to use auto-tuning based upon the memory size of the host. 

* All global and daemon-specific heap size variables now support units.  If the 
variable is only a number, the size is assumed to be in megabytes.

  was:
* The default heap sizes have been removed and the HADOOP_HEAPSIZE variable has 
been deprecated  (It will still be honored if set, but expect it to go away in 
the future).  This will allow for the JVM to use auto-tuning based upon the 
memory size of the host.  To re-enable the old default, configure 
HADOOP_HEAPSIZE_MAX="1g" in hadoop-env.sh.

* All global and daemon-specific heap size variables now support units.  If the 
variable is only a number, the size is assumed to be in megabytes.


> rework  heap management  vars
> -----------------------------
>
>                 Key: HADOOP-10950
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10950
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: scripts
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>              Labels: scripts
>         Attachments: HADOOP-10950-01.patch, HADOOP-10950-02.patch, 
> HADOOP-10950.patch
>
>
> 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.3.4#6332)

Reply via email to