[
https://issues.apache.org/jira/browse/OOZIE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717733#comment-13717733
]
Alejandro Abdelnur commented on OOZIE-1461:
-------------------------------------------
Doing an upgrade is a series of manual steps and verifications, for upgrades of
the Oozie server, the sharelibs or both.
By using a different directory every time a sharelib is updated (regardless of
the Oozie server being upgraded) ...
* push new sharelib to a new HDFS dir
* update oozie-site.xml with new sharelib location
* restart oozie server
... you don't disrupt any running job in the cluster, and the new sharelib dir
gets picked up after the Oozie server restart.
And these steps can be automated if necessary to avoid human errors.
Option #3 seems to me unnecessary complexity that will require checks to ensure
dangling old dirs are not left behind.
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.
IMO, this seems to be too much complexity for what is worth.
> 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
