[
https://issues.apache.org/jira/browse/OOZIE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715740#comment-13715740
]
Robert Kanter commented on OOZIE-1461:
--------------------------------------
That's a good point.
Eventually (Oozie 5?) isn't the idea to make oozie.action.ship.launcher.jar =
false by default? The launcher jar classes would be picked up from the
sharelibs. In the meantime, (Oozie 4), the default is to keep the current
behavior of uploading the launcher jar.
After reading the description of the property in oozie-default.xml in the
patch, it sounds like we would have the following:
# current behavior where launcher jar gets uploaded for each action
(oozie.action.ship.launcher.jar=true)
# launcher classes get picked up from sharelib
(oozie.action.ship.launcher=false and
oozie.service.ActionService.launcherjar.libpath.upload=false)
# launcher classes get picked up from launcher jar that Oozie uploaded at
startup to temp location (at oozie.service.WorkflowAppService.system.libpath)
in HDFS and get purged after a configurable amount of days to get reuploaded
(oozie.action.ship.launcher=false and
oozie.service.ActionService.launcherjar.libpath.upload=true)
What is the motivation for adding a third way of dealing with the launcher
classes?
> 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
