Urmi Mustafi created GOBBLIN-2086:
-------------------------------------

             Summary: Allow multiple reminders for the same dagAction in 
DagActionReminderScheduler
                 Key: GOBBLIN-2086
                 URL: https://issues.apache.org/jira/browse/GOBBLIN-2086
             Project: Apache Gobblin
          Issue Type: Bug
          Components: gobblin-service
            Reporter: Urmi Mustafi
            Assignee: Abhishek Tiwari


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",



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to