[
https://issues.apache.org/jira/browse/OOZIE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715916#comment-13715916
]
Robert Kanter commented on OOZIE-1461:
--------------------------------------
Chatted with Alejandro, and he pointed out that if you use a new sharelib for
the upgrade, it won't kill the running jobs (that's essentially what you're
doing with the #3). For example, if you have your sharelib at
{{/user/oozie/3.3.1/share/lib}} you can make the next one at
{{/user/ozoie/3.3.2/share/lib}} when doing the upgrade.
Though I suppose that this is a manual change the admins would have to manage.
> 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
