Harsh J created OOZIE-2504:
------------------------------
Summary: Create a log4j.properties under HADOOP_CONF_DIR in Shell
Action
Key: OOZIE-2504
URL: https://issues.apache.org/jira/browse/OOZIE-2504
Project: Oozie
Issue Type: Improvement
Components: action
Affects Versions: trunk
Reporter: Harsh J
Assignee: Harsh J
Priority: Minor
We currently do environment exports of {{HADOOP_CONF_DIR}} and
{{YARN_CONF_DIR}}, when the feature of config directory is enabled, for
catering to people wanting to use {{hadoop}} or such relying commands, and this
works well.
However, an issue occurs when {{<capture-output/>}} is enabled, wherein the
commands, not finding a logger configuration, start using {{System.out}} by
default [1], and any/all lines that match the capture output criteria from the
log-spam in {{System.out}} make it into the captured results, which can break
further logic done in subsequent actions relying on proper captured values.
We can fix this by pre-preparing, optionally, a {{log4j.properties}} file under
{{HADOOP_CONF_DIR}} and {{YARN_CONF_DIR}}, such that the commands use that
logging configuration and write logs into {{System.err}} by default.
[1] -
https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/ConsoleAppender.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
