[
https://issues.apache.org/jira/browse/GOBBLIN-1920?focusedWorklogId=881800&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-881800
]
ASF GitHub Bot logged work on GOBBLIN-1920:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Sep/23 23:02
Start Date: 25/Sep/23 23:02
Worklog Time Spent: 10m
Work Description: umustafi commented on PR #3788:
URL: https://github.com/apache/gobblin/pull/3788#issuecomment-1734578922
> nice catch! I was wondering if it even makes sense for us to provide
`eventTimeMillis` to the method signature of `scheduleReminderForEvent`.
Earlier we were using it to create `JobDetail`, but now the only place we use
it is for logging and the info that it conveys is the clock drift (which we
might be okay not logging)... let me know what's your take?
I am leaving it in to catch that clock drift in time being. I suspect it's
not the root of our problem but until we are reliably bug free keeping logs in.
Issue Time Tracking
-------------------
Worklog Id: (was: 881800)
Time Spent: 40m (was: 0.5h)
> Use DB event timestamp for MA Reminder events
> ---------------------------------------------
>
> Key: GOBBLIN-1920
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1920
> Project: Apache Gobblin
> Issue Type: Bug
> Components: gobblin-service
> Reporter: Urmi Mustafi
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When setting the reminder event we use the trigger time local to each host.
> Instead we want to use the timestamp from database to see consistency between
> hosts in case their clock drift is significant.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
