You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2014/04/08 00:38:15 UTC
[jira] [Created] (OOZIE-1783) Sharelib purging only occurs at Oozie
startup
Robert Kanter created OOZIE-1783:
------------------------------------
Summary: 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
Priority: Critical
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)