[
https://issues.apache.org/jira/browse/OOZIE-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762124#comment-13762124
]
Rohini Palaniswamy commented on OOZIE-1518:
-------------------------------------------
Was actually not aware that OozieSharelibCLI was available for admins to copy
sharelib jars. That step will remain as is. Only the behavior will change.
Currently running oozie-setup.sh sharelib -update, it will delete the current
sharelib directory and copy the files again. So all the jobs in flight will
fail (Filenotfoundexception, Permission denied exception, The distributed cache
object
changed during the job exception, etc).
OozieSharelibCLI should now be modified to copy to the sharelib staging
directory and then issue the oozie cli admin sharelib update web service call.
The web service call will make Oozie server pick up the jars from staging
directory and create a new tmpYYYYMMDD folder and copy the new jars. Older jobs
will continue to run off the older tmpYYYYMMDD directory and new jobs will use
the new tmp directory. The main purpose is to not have any jobs fail during
Oozie server upgrades or sharelib upgrades when pig/hive upgrades.
> 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
