[
https://issues.apache.org/jira/browse/OOZIE-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760293#comment-13760293
]
Robert Kanter commented on OOZIE-1518:
--------------------------------------
so you want to do this?
- User puts sharelib dirs under here {{/user/oozie/share/lib-staging}}
- Oozie server(s) copy that to {{/user/oozie/share/lib}} on startup
- Admin command only has to have one server act because there's no local dir
I see some advantages to this:
# HA simplified; syncing staging and sharelib is only one direction
# Doesn't require access to local machine(s) where Oozie is
I also see some disadvantages:
# Sharelib takes even more space in HDFS (though HDFS is supposed to be big so
its probably okay)
# Users still have to manually upload sharelib
That last disadvantage seems like a big one to me. One nice thing of the
original plan was that the sharelib would be mostly handled by Oozie
automatically; the user only has to do something if they want to put custom
jars in it. With this new plan, they still have to upload the sharelib to the
staging dir in HDFS, which is one of the things we were trying to get rid of.
> Copy action sharelib jars from hdfs
> ------------------------------------
>
> Key: OOZIE-1518
> URL: https://issues.apache.org/jira/browse/OOZIE-1518
> Project: Oozie
> Issue Type: Bug
> Reporter: Virag Kothari
>
> OOZIE-1461 will copy the launcher related sharelib jars from Oozie's
> classpath to hdfs.
> This JIRA aims to copy the jars from an hdfs staging dir. This staging dir
> will typically contain action related jars.
> OOZIE-1461 always creates a sharelib with new timestamp. This JIRA will make
> sure that only if either the action jars or launcher jars are modified, then
> a new sharelib is created.
>
--
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
