[ 
https://issues.apache.org/jira/browse/GOBBLIN-1999?focusedWorklogId=903449&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-903449
 ]

ASF GitHub Bot logged work on GOBBLIN-1999:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/Feb/24 22:57
            Start Date: 02/Feb/24 22:57
    Worklog Time Spent: 10m 
      Work Description: Will-Lo merged PR #3874:
URL: https://github.com/apache/gobblin/pull/3874




Issue Time Tracking
-------------------

    Worklog Id:     (was: 903449)
    Time Spent: 40m  (was: 0.5h)

> Fix GaaS flowstatus reporting when multiple leaders execute flow
> ----------------------------------------------------------------
>
>                 Key: GOBBLIN-1999
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1999
>             Project: Apache Gobblin
>          Issue Type: Bug
>            Reporter: William Lo
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> In GaaS multileader there is a race condition where one host will 
> compile/kick off a job, and the other hosts have an expected behavior of 
> compiling the job but avoiding submission until the DagManager supports 
> multiple leaders. The other hosts that run slower will try to check if the 
> current job is running, and then mark the flow as failed at the same time 
> when the leader submits the job. This leads to scenarios where successful 
> flows can be marked as failed flows.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to