[ https://issues.apache.org/jira/browse/HADOOP-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved HADOOP-11058. --------------------------------------- Resolution: Fixed Fix Version/s: 3.0.0 Committed. :) > 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 > Fix For: 3.0.0 > > Attachments: HADOOP-11058.1.patch, HADOOP-11058.2.patch, > HADOOP-11058.3.patch, HADOOP-11058.4.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)