[
https://issues.apache.org/jira/browse/HADOOP-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120040#comment-14120040
]
Allen Wittenauer commented on HADOOP-11058:
-------------------------------------------
This is also true for branch-2, so marking this as an improvement.
In particular, I noticed logging going haywire. As mentioned in HADOOP-10879,
log4j settings should almost certainly be found.
> 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
> Labels: newbie
>
> 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)
