[OOZIE-1783] Sharelib purging only occurs at Oozie startup

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: trunk
• Fix Version/s: 4.1.0
• Assignee: Robert Kanter
• Reporter: Robert Kanter
• Created: 07/Apr/14 22:37
• Updated: 09/Dec/14 00:44
• Resolved: 23/May/14 00:26

Description

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.