[GOBBLIN-2086] Allow multiple reminders for the same dagAction in DagActionReminderScheduler

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: gobblin-service
• Assignee: Abhishek Tiwari
• Reporter: Urmi Mustafi
• Created: 12/Jun/24 19:36
• Updated: 19/Jul/24 20:28

Description

An ObjectAlreadyExistsException is thrown by the QuartzScheduler for deadline dagAction types when attempting to set a reminder on the lease of a deadline dagAction type because the original (non-reminder) job may still exist in the DagActionReminderScheduler. It's a non-fatal exception to have redundant reminders on the same dagAction so the code change gracefully handles this problem.

 

Exception: 

Unable to store Job : '[flowgroup].[flowname].[flowid].ENFORCE_JOB_START_DEADLINE', because one already exists with this identification.","stackTrace":[{"index":0,"call":"storeJob","columnNumber":null,"fileName":"RAMJobStore.java","lineNumber":279,"nativeMethod":"0","source":"org.quartz.simpl.RAMJobStore"},{"index":1,"call":"storeJobAndTrigger",