[
https://issues.apache.org/jira/browse/GOBBLIN-1778?focusedWorklogId=843952&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-843952
]
ASF GitHub Bot logged work on GOBBLIN-1778:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Feb/23 22:16
Start Date: 06/Feb/23 22:16
Worklog Time Spent: 10m
Work Description: ZihanLi58 merged PR #3635:
URL: https://github.com/apache/gobblin/pull/3635
Issue Time Tracking
-------------------
Worklog Id: (was: 843952)
Time Spent: 50m (was: 40m)
> Add house keeping thread in DagManager to periodically sync in memory state
> with mysql table
> ---------------------------------------------------------------------------------------------
>
> Key: GOBBLIN-1778
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1778
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Zihan Li
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Now dag managers have the assumption that it is the only process that can
> update mysql table and the in-memory state is always in sync with mysql. But
> we do notice that during the leader transforms period, it's possible that two
> dag manager can run concurrently and update the mysql db at the same time.
> To address that, we need either add a lock to make sure only one dag manager
> is working at one time, or we need to have a housekeeping thread to
> periodically sync the in-memory state with the mysql table. After discussion,
> we choose to go with later approach
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
