[
https://issues.apache.org/jira/browse/OOZIE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717763#comment-13717763
]
Rohini Palaniswamy commented on OOZIE-1461:
-------------------------------------------
bq. Option #3 seems to me unnecessary complexity that will require checks to
ensure dangling old dirs are not left behind.
Doing manual steps adds complexity and we want to move away from as much
manual steps as possible. Older dirs can be easily cleaned up on restart and
since these jars hardly take few MBs DFS space will not be occupied too much
even if Oozie is restarted frequently. This is something we did in GDM (Y!
internal product for data management) 3 years ago and has been working so well.
bq. Also, with Oozie HA coming, we'll have to have a switch to enabled/disable
this per Oozie instance (making the config of de instances diferent) plus we'll
have to use ZK to communicate to the other Oozie instance where the temp dir is
for the current run. And if the oozie instance responsible for pushing the
launcher jar to temp dir is restarted, the other oozie instance will have to
pick up the new temp dir on the flight.
None of the above is required. Each oozie server will have its own temp
directory containing launcher jars and the temp directory stays in memory and
used till the server is restarted. Each oozie might be running different
versions if we are doing a rolling upgrade and cannot share the launcher jars.
> 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
