[
https://issues.apache.org/jira/browse/GOBBLIN-1784?focusedWorklogId=845993&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-845993
]
ASF GitHub Bot logged work on GOBBLIN-1784:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Feb/23 20:19
Start Date: 16/Feb/23 20:19
Worklog Time Spent: 10m
Work Description: Will-Lo merged PR #3641:
URL: https://github.com/apache/gobblin/pull/3641
Issue Time Tracking
-------------------
Worklog Id: (was: 845993)
Time Spent: 1h 40m (was: 1.5h)
> Race condition where on service restart DagManager will lose track of dags
> --------------------------------------------------------------------------
>
> Key: GOBBLIN-1784
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1784
> Project: Apache Gobblin
> Issue Type: Bug
> Components: gobblin-service
> Reporter: William Lo
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Gobblin-as-a-Service has a bug where on restart, the DagManager will clean up
> dags but a flow event is never sent.
> This leads to a scenario where if the event is never sent by the underlying
> notification system, the dag will already be cleaned up and thus the job
> status will permanently be stuck in a running state.
> The DagManager thus should only clean up its own reference of dags after it
> reads that the jobstatus monitor has properly saved the final flow status,
> and if a status hasn't been received by some timestamp (e.g. 5 mins), then
> the DagManager will re-emit the event in case it was lost.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
