Inconsistency in schedule store can silently prevent scheduler from starting up
Description
Release Notes
None
Activity
Show:
Bhooshan Mogal June 12, 2020 at 10:26 PM
Haven't seen this in a while, let's re-open if it happens again.
Chengfeng Mao June 21, 2017 at 1:18 AM
Actually, QuartzScheduler object will be only created once no matter the number of retries, because TimeScheduler will only be created once and there will be only one Supplier<org.quartz.Scheduler> injected into TimeScheduler
Ali Anwar June 21, 2017 at 12:54 AM
Also, each time, we create a new QuartzScheduler object, which ends up creating a new QuartzSchedulerThread each retry.
https://github.com/caskdata/cdap/blob/v4.1.0/cdap-app-fabric/src/main/java/co/cask/cdap/app/guice/AppFabricServiceRuntimeModule.java#L403
Cannot Reproduce
Pinned fields
Click on the next to a field label to start pinning.
Created June 21, 2017 at 12:25 AM
Updated June 12, 2020 at 10:26 PM
Resolved June 12, 2020 at 10:26 PM
If the trigger exists for a schedule, but the job doesn't exist, the scheduler will repeatedly restart and have the following exception: