[
https://issues.apache.org/jira/browse/OOZIE-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000318#comment-14000318
]
Purshotam Shah commented on OOZIE-1783:
---------------------------------------
[~rohini]
Yes, we need to move purgeLibs(fs, LAUNCHER_PREFIX, current) out of
isFirstServer().
Purging sharelib in HA can be slightly complicated, we can create a different
JIRA for that.
> Sharelib purging only occurs at Oozie startup
> ---------------------------------------------
>
> Key: OOZIE-1783
> URL: https://issues.apache.org/jira/browse/OOZIE-1783
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Critical
> Attachments: OOZIE-1783.patch, OOZIE-1783.patch
>
>
> The purgeLibs method only gets called on startup of the first Oozie server.
> This means that if you update the sharelib without restarting Oozie, then
> Oozie will never clean up the old sharelibs and launcherlibs until you
> restart the server. In fact, with Oozie HA, it will never clean up unless
> you restart all of the servers at the same time (in other words, a rolling
> restart or just restarting one Oozie will never cause purgeLibs to get
> called).
> This should be moved into a background thread (i.e. scheduled with
> SchedulerService) to run periodically. Once a day is probably good enough,
> but we could make it configurable if needed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
