[
https://issues.apache.org/jira/browse/HADOOP-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256901#comment-14256901
]
Allen Wittenauer commented on HADOOP-11058:
-------------------------------------------
After thinking about this for a few days, I think this is a fine solution. A
warning that log4j bits are missing for daemons is a huge indicator that things
are wrong. IMO, we should expand the message to indicate that $HADOOP_CONF_DIR
may be incomplete or broken or whatever beyond just that the file is missing
though.
Also, we need this same code in the secure version of the wrapper as well.
> Missing HADOOP_CONF_DIR generates strange results
> -------------------------------------------------
>
> Key: HADOOP-11058
> URL: https://issues.apache.org/jira/browse/HADOOP-11058
> Project: Hadoop Common
> Issue Type: Improvement
> Components: scripts
> Reporter: Allen Wittenauer
> Assignee: Masatake Iwasaki
> Labels: newbie
> Attachments: HADOOP-11058.1.patch
>
>
> If HADOOP_CONF_DIR is defined but points to a directory that either doesn't
> exist or isn't actually a viable configuration directory, all sorts of weird
> things happen, especially for logging. The shell code should do a better job
> of verifying the directory is valid and exit if it detects if it is broken in
> some way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
