[ https://issues.apache.org/jira/browse/YARN-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130924#comment-16130924 ]
Allen Wittenauer commented on YARN-7011: ---------------------------------------- bq. Is that example different than when --config is used to point to that exact same misconfigured directory? Yes. branch-2's code decided that it was going to ignore what was in the configuration directory as told to us by the user. Actually, I'm wrong. branch-2 does exactly what trunk does: {code} hadoop-2.8.1 aw$ grep HADOOP_CONF_DIR etc/hadoop/hadoop-env.sh export HADOOP_CONF_DIR=/bin hadoop-2.8.1 aw$ bin/hadoop --config etc/hadoop classpath /bin:/private/tmp/hadoop-2.8.1/share/hadoop/common/lib/*: ... {code} So the behavior is exactly the same... > 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 > > 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