hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7011) yarn-daemon.sh is not respecting --config option
Date Wed, 16 Aug 2017 19:55:00 GMT

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

Allen Wittenauer commented on YARN-7011:
----------------------------------------

The classpath output is important because one of the first entries should be the HADOOP_CONF_DIR.
 We won't see that in the direct output of the resourcemanager subcommand.  (It might be in
the daemon's .out file though.  I can't remember.)

bq. "DEBUG: Profiles: importing /tmp/hadoop/"

If this is missing, then that likely means your copy of the config directory is incomplete.
 Likely a result of cp -p * instead of cp -pr *.

But anyway...

bq. Yes we set HADOOP_CONF_DIR in our env.sh file

There's the problem then.  Remove it.  Setting HADOOP_CONF_DIR in *-env.sh effectively resets
the config directory back to wherever it is set. It acts as an *override* to the --config
option in 3.x.

One other note.  The command you've provided for starting the resourcemanager is probably
the hardest way to start the RM in 3.x . :)  You can set YARN_RESOURCEMANAGER_USER=yarn in
hadoop-env/yarn-env.sh and then just use {{yarn --daemon start resourcemanager}} as root.
 It will switch users for you prior to start.

> yarn-daemon.sh is not respecting --config option
> ------------------------------------------------
>
>                 Key: YARN-7011
>                 URL: https://issues.apache.org/jira/browse/YARN-7011
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>            Reporter: Sumana Sathish
>            Priority: Blocker
>             Fix For: 3.0.0-beta1
>
>
> Steps to reproduce:
> 1. Copy the conf to a temporary location /tmp/Conf
> 2. Modify anything in yarn-site.xml under /tmp/Conf/. Ex: Give invalid RM address
> 3. Restart the resourcemanager using yarn-daemon.sh using --config /tmp/Conf
> 4. --config is not respected as the changes made in /tmp/Conf/yarn-site.xml is not taken
in while restarting RM



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message