[ 
https://issues.apache.org/jira/browse/GOBBLIN-2086?focusedWorklogId=923174&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-923174
 ]

ASF GitHub Bot logged work on GOBBLIN-2086:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 12/Jun/24 19:41
            Start Date: 12/Jun/24 19:41
    Worklog Time Spent: 10m 
      Work Description: umustafi commented on PR #3971:
URL: https://github.com/apache/gobblin/pull/3971#issuecomment-2163772346

   Actually thinking over this a second time, I don't think the original 
(non-reminder) job will still exist in the scheduler bc it should have been 
deleted since it was an "orphan" after the deadline passed and the trigger 
fired. I'm trying to validate why we may end up with multiple reminders than 
for this type of event. Let me know if you have thoughts.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 923174)
    Time Spent: 20m  (was: 10m)

> 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
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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