[OOZIE-1461] provide an option to auto-deploy launcher jar onto HDFS system libpath

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk
• Fix Version/s: 4.1.0
• Assignee: Virag Kothari
• Reporter: Ryota Egashira
• Created: 22/Jul/13 17:44
• Updated: 09/Dec/14 00:45
• Resolved: 06/Sep/13 16:22

Description

after OOZIE-1311, 1315, when oozie.action.ship.launcher.jar is false, launcher jar is shipped from sharelib, but it requires manual process for admin people to upload jar files onto the sharelib at server-start time, before actually starting running workflow actions. This JIRA to provide an option to remove the manual process, and make oozie server (ActionService) to automatically create and upload launcher jar files onto HDFS (tmp directory under oozie.service.WorkflowAppService.system.libpath), and allow workflow actions to consume from there. every time oozie server starts, it automatically creates a new directory to upload launcher jars to, and also purges stale directories previously created (older than 7 days, configurable).
if false (which is current default). the behavior is the same with previous, launcher jars provided from sharelib (when oozie.action.ship.launcher.jar=false) or each workflow action creates and ships launcher jar (when oozie.action.ship.launcher.jar=true)

Issue Links

• breaks: OOZIE-1528 CoordRerunX and ActionEndX not updating some of the modified beans.
• relates to: OOZIE-1518 Copy action sharelib jars from hdfs
• relates to: OOZIE-1519 Admin command to update the sharelib