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

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

                Author: ASF GitHub Bot
            Created on: 03/Dec/21 22:40
            Start Date: 03/Dec/21 22:40
    Worklog Time Spent: 10m 
      Work Description: arjun4084346 commented on pull request #3439:
URL: https://github.com/apache/gobblin/pull/3439#issuecomment-985890123


   I worked on this issue before https://github.com/apache/gobblin/pull/3314 
closed without merge because the approach of merging was not accepted.
   The base condition why this issue will appear is that events should arrive 
out of order. With some internal fixes that made sure that all the GTEs for a 
flow are sent to the same kafka partition, I made sure that events arrive in 
order. So this issue should not appear.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 690368)
    Time Spent: 1h 40m  (was: 1.5h)

> GaaS (DagManager) keep retrying a failed job beyond max attempt number
> ----------------------------------------------------------------------
>
>                 Key: GOBBLIN-1585
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1585
>             Project: Apache Gobblin
>          Issue Type: Improvement
>            Reporter: Zihan Li
>            Priority: Major
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> The issue is that for the same flow execution, we don't receive the event in 
> order. if the job fail and we retry, we may receive running event first, and 
> then the Orchestrate event which update the current attempts and should retry 
> value will be ignored and cause to job to continually try to retrying util 
> the running job finished.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to