[
https://issues.apache.org/jira/browse/YARN-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129757#comment-16129757
]
Junping Du commented on YARN-7011:
----------------------------------
bq. 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.
Why setting HADOOP_CONF_DIR in env is supposed to override --config specified
in yarn or hadoop CLI? This will be a regression since 2.x as existing Hadoop
user (and cluster management tools) will get affected.
Set back to blocker for 3.0 beta.
> 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: Trivial
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
