hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-115) yarn commands shouldn't add "m" to the heapsize
Date Sun, 23 Sep 2012 04:05:07 GMT

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

Harsh J commented on YARN-115:
------------------------------

Do we even need these specific specifiers? Most users have been content with injecting their
own style of -Xmx into the *_OPTS parameters today? Though yeah, that *shouldn't* have been
the case.
                
> yarn commands shouldn't add "m" to the heapsize
> -----------------------------------------------
>
>                 Key: YARN-115
>                 URL: https://issues.apache.org/jira/browse/YARN-115
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 0.23.3
>            Reporter: Thomas Graves
>
> the yarn commands add "m" to the heapsize. This is unlike the hdfs side and the the old
jt/tt used to do.
>     JAVA_HEAP_MAX="-Xmx""$YARN_RESOURCEMANAGER_HEAPSIZE""m"
>     JAVA_HEAP_MAX="-Xmx""$YARN_NODEMANAGER_HEAPSIZE""m"
> We should not be adding in the "m" and allow the user to specify units.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message