[ https://issues.apache.org/jira/browse/OOZIE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715820#comment-13715820 ]
Alejandro Abdelnur commented on OOZIE-1461: ------------------------------------------- why do we need #3? I think this is not necessary. If you want a performance boost just use #2. If you are using sharelibs, you can just set the config for #2 and it will work, nothing additional to do. > 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