[
https://issues.apache.org/jira/browse/GOBBLIN-2086?focusedWorklogId=923181&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-923181
]
ASF GitHub Bot logged work on GOBBLIN-2086:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Jun/24 21:45
Start Date: 12/Jun/24 21:45
Worklog Time Spent: 10m
Work Description: arjun4084346 commented on PR #3971:
URL: https://github.com/apache/gobblin/pull/3971#issuecomment-2163955807
because dagActionQueue is threadsafe, two threads should not pull out the
same dag action and try to set reminder for it. it seems there is something
more to this issue.
Issue Time Tracking
-------------------
Worklog Id: (was: 923181)
Time Spent: 1h (was: 50m)
> 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: 1h
> 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)
