[
https://issues.apache.org/jira/browse/GOBBLIN-1585?focusedWorklogId=690343&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-690343
]
ASF GitHub Bot logged work on GOBBLIN-1585:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Dec/21 21:55
Start Date: 03/Dec/21 21:55
Worklog Time Spent: 10m
Work Description: arjun4084346 commented on pull request #3439:
URL: https://github.com/apache/gobblin/pull/3439#issuecomment-985869414
Can you point me to the code where DagManager checks if the "current attempt
number" is less than the "max allowed attempt number" ? Does it fetch the
currentAttempt from the job status store?
--
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: 690343)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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)
