[OOZIE-2844] Increase stability of Oozie actions when log4j.properties is missing or not readable

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.3.0
• Fix Version/s: 5.0.0b1
• Component/s: action
• Assignee: Andras Piros
• Reporter: Andras Piros
• Created: 24/Mar/17 12:15
• Updated: 25/Jan/18 21:00
• Resolved: 06/Apr/17 14:21

Description

In several Oozie actions we face the problem that if log4j.properties is not readable by current thread, or not present on the classpath, while taking an URL.openStream() call afterwards, an IOException is thrown and the action won't run.

Such actions are:

• DistcpMain
• HiveMain
• PigMain
• PigMainWithOldApi
• SparkMain
• SqoopMain

Extend LauncherMain.run() by a convenience method that loads Hadoop's log4j.properties in beforehand. In case URL.openStream() would throw IOException we resort to a call to a new file hadoop-default-log4j.properties on the classpath (packaged along w/ LauncherMain.class) that has the same contents as the log4j.properties that is not accessible / readable / present.

Issue Links

• links to: ReviewBoard link