hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6168) HADOOP_HEAPSIZE cannot be done per-server easily
Date Fri, 24 Jul 2009 03:52:14 GMT

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

Vinod K V commented on HADOOP-6168:
-----------------------------------


Though not the cleanest, there is a way to do this using various HADOOP_*_OPTS. We can set
heap size also in these opts, for e.g. HADOOP_JOBTRACKER_OPTS=-Xmx2000m, it will be eventually
picked up by the running command. It works this way because jvm takes up the last -Xmx value
that occurs in the command line which would be from HADOOP_OPTS.

{code} exec "$JAVA" $JAVA_HEAP_MAX $HADOOP_OPTS $CLASS "$@"{code}

> HADOOP_HEAPSIZE cannot be done per-server easily
> ------------------------------------------------
>
>                 Key: HADOOP-6168
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6168
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.18.3
>            Reporter: Allen Wittenauer
>
> The hadoop script forces a heap that cannot be easily overridden if one wants to push
the same config everywhere.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message