Urmi Mustafi created GOBBLIN-1921:
-------------------------------------
Summary: Properly handle reminder events
Key: GOBBLIN-1921
URL: https://issues.apache.org/jira/browse/GOBBLIN-1921
Project: Apache Gobblin
Issue Type: Bug
Components: gobblin-service
Reporter: Urmi Mustafi
Assignee: Abhishek Tiwari
Reminder flow trigger events were being improperly handled and interpreted as
new events because they are triggered {{linger}} time after the original
trigger where {{epsilon < linger}} and we use {{epsilon}} to determine event
distinctness. With reminder events being considered distinct events, we were
launching excess concurrent flows that were then being cancelled. Now we handle
reminder events differently from normal event triggers to ensure they're
properly evaluated. Because of db laundering, reminder events are easy to
handle - if they're older than the currently worked upon event in the database
they can be skipped and if they're equal to the current event in the database
they are handled like normal. Reminder events should never be newer than the
current event in the lease arbiter table because db laundering always results
in increasing event times.Â
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
