You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (Commented) (JIRA)" <ji...@apache.org> on 2011/12/20 08:09:30 UTC
[jira] [Commented] (MAPREDUCE-3578) starting nodemanager as 'root'
gives "Unknown -jvm option"
[ https://issues.apache.org/jira/browse/MAPREDUCE-3578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172992#comment-13172992 ]
Allen Wittenauer commented on MAPREDUCE-3578:
---------------------------------------------
Chances are high that your jsvc is busted in some way or you are running in secure mode or something similar. It might just need to be recompiled the proper bitness. In any case "-jvm server" is a jsvc option used only when the daemon is run as root, thus why it is required for $EUID = 0. "-server" is a JVM option and used when the daemon is run by not root.
> starting nodemanager as 'root' gives "Unknown -jvm option"
> ----------------------------------------------------------
>
> Key: MAPREDUCE-3578
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3578
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 0.23.0
> Environment: jdk 1.6.0.26, ubuntu 11.04
> Reporter: Gilad Wolff
>
> running "sudo HADOOP_ROOT/bin/yarn-daemon.sh start nodemanager" I get "unknown -jvm option" (jdk version 1.6.0.26). The problem seems to be with line 204 in yarn:
> elif [ "$COMMAND" = "nodemanager" ] ; then
> CLASSPATH=${CLASSPATH}:$YARN_CONF_DIR/nm-config/log4j.properties
> CLASS='org.apache.hadoop.yarn.server.nodemanager.NodeManager'
> if [[ $EUID -eq 0 ]]; then
> YARN_OPTS="$YARN_OPTS -jvm server $YARN_NODEMANAGER_OPTS"
> else
> YARN_OPTS="$YARN_OPTS -server $YARN_NODEMANAGER_OPTS"
> fi
> using -server seems to solve the problem for me.
> I tested using build 929 from https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Mapreduce-trunk/.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira