You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2013/05/14 00:25:16 UTC

[jira] [Commented] (YARN-356) Add YARN_NODEMANAGER_OPTS and YARN_RESOURCEMANAGER_OPTS to yarn.env

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

Harsh J commented on YARN-356:
------------------------------

Hey Lohit,

I think we can doc these on the yarn-env.sh template we ship, to make users aware of its presence. I hadn't closed the ticket due to that non-doc factor, but wanted to note that these are already being looked-for.
                
> Add YARN_NODEMANAGER_OPTS and YARN_RESOURCEMANAGER_OPTS to yarn.env
> -------------------------------------------------------------------
>
>                 Key: YARN-356
>                 URL: https://issues.apache.org/jira/browse/YARN-356
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager, resourcemanager
>    Affects Versions: 2.0.2-alpha
>            Reporter: Lohit Vijayarenu
>
> At present it is difficult to set different Xmx values for RM and NM without having different yarn-env.sh. Like HDFS, it would be good to have YARN_NODEMANAGER_OPTS and YARN_RESOURCEMANAGER_OPTS

--
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