[ https://issues.apache.org/jira/browse/OOZIE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715769#comment-13715769 ]
Robert Kanter commented on OOZIE-1461: -------------------------------------- Ah, I misunderstood that; this is to change 1 to 3 and leave 2 alone. The performance hit of 1 was one of the motivations for 2. Changing 1 to 3 sounds like a good idea. Besides the performance improvement, this would also fix the problem where the local temp dir gets cleaned up while Oozie is running causing Oozie to be unable to find and upload the launcher jar. One concern I'd have is what happens if Oozie is replacing the stale launcher jars at the same time as an action starts and needs one of the launcher jars? I know that [~tucu00] has had some thoughts on the launcher jar before; [~tucu00], any thoughts on this change? > provide an option to auto-deploy launcher jar onto HDFS system libpath > ---------------------------------------------------------------------- > > Key: OOZIE-1461 > URL: https://issues.apache.org/jira/browse/OOZIE-1461 > Project: Oozie > Issue Type: Bug > Affects Versions: trunk > Reporter: Ryota Egashira > Assignee: Ryota Egashira > Fix For: trunk > > > 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira