public class OldJobReaper extends InterruptingScheduledService
1. A job that's deployed should NOT BE reaped regardless of its history or creation date. 2. A job not deployed, with history, and an event before the number of retention days should BE reaped. 3. A job not deployed, with history, and an event after the number of retention days should NOT BE reaped. An example is a job created a long time ago but deployed recently. 4. A job not deployed, without history, and without a creation date should BE reaped. Only really old versions of Helios create jobs without dates. 5. A job not deployed, without history, and with a creation date before the number of retention days should BE reaped. 6. A job not deployed, without history, and with a creation date after the number of retention days should NOT BE reaped.
Note that the --disable-job-history flag in AgentParser
controls whether the Helios agent should write job history to the data store. If this is
disabled, scenarios two and three above will never match. In this case, a job created a long
time ago but deployed recently may be reaped once it's undeployed even if the user needs it
again in the future.
| Constructor and Description |
|---|
OldJobReaper(MasterModel masterModel,
long retentionDays) |
| Modifier and Type | Method and Description |
|---|---|
protected void |
runOneIteration() |
protected ScheduledFuture<?> |
schedule(Runnable runnable,
ScheduledExecutorService executorService) |
beforeIteration, shutDown, startUppublic OldJobReaper(MasterModel masterModel, long retentionDays)
protected void runOneIteration()
runOneIteration in class InterruptingScheduledServiceprotected ScheduledFuture<?> schedule(Runnable runnable, ScheduledExecutorService executorService)
schedule in class InterruptingScheduledServiceCopyright © 2017. All rights reserved.