[
https://issues.apache.org/jira/browse/GOBBLIN-1585?focusedWorklogId=690324&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-690324
]
ASF GitHub Bot logged work on GOBBLIN-1585:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Dec/21 21:11
Start Date: 03/Dec/21 21:11
Worklog Time Spent: 10m
Work Description: ZihanLi58 opened a new pull request #3439:
URL: https://github.com/apache/gobblin/pull/3439
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I
have checked off all the steps below!
### JIRA
- [ ] My PR addresses the following [Gobblin
JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references
them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
- https://issues.apache.org/jira/browse/GOBBLIN-1585
### Description
- [ ] Here are some details about my PR, including screenshots (if
applicable):
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.
Add low/high water info in cluster event metadata generator since
jobStateEvent will not been processed for job status
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
Unit test
### Commits
- [ ] My commits all reference JIRA issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
2. Subject is limited to 50 characters
3. Subject does not end with a period
4. Subject uses the imperative mood ("add", not "adding")
5. Body wraps at 72 characters
6. Body explains "what" and "why", not "how"
--
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: 690324)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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)
