-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[BEAM-11377] Fix retry & cleanup issues. #14026
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Run Dataflow PostRelease |
|
Run Python_PVR_Flink PreCommit |
35f23dc to
a109916
Compare
|
Run Dataflow PostRelease |
Codecov Report
@@ Coverage Diff @@
## master #14026 +/- ##
==========================================
+ Coverage 82.97% 82.99% +0.01%
==========================================
Files 469 469
Lines 58294 58298 +4
==========================================
+ Hits 48371 48382 +11
+ Misses 9923 9916 -7
Continue to review full report at Codecov.
|
a109916 to
d894253
Compare
|
Run Dataflow PostRelease |
d894253 to
906e658
Compare
|
Run Dataflow PostRelease |
906e658 to
3517e37
Compare
|
Run Dataflow PostRelease |
- Also fixes [BEAM-9970]. - Attempt to reduce 'Connection Reset' errors with mvn wagon flags. - Fix shutdown process that fails when the job is not in state Running.
3517e37 to
baf927c
Compare
|
Run Dataflow PostRelease |
|
Run Java_Examples_Dataflow_Java11 PreCommit |
|
Run Python PreCommit |
|
Run PythonDocker PreCommit |
|
R: @pabloem |
pabloem
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Just one question.
| t.run("""RUNNING_JOB=`gcloud dataflow jobs list | grep ${jobName} | grep Running | cut -d' ' -f1` | ||
| if [ ! -z "\${RUNNING_JOB}" ] | ||
| then | ||
| gcloud dataflow jobs cancel \${RUNNING_JOB} | ||
| else | ||
| echo "Job '${jobName}' is not running." | ||
| fi | ||
| """) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does it make sense to retry? are jobs here usually finished/cancelled, or pending?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Jobs were finished/cancelled during my testing. I didn't see any in pending, there are a lot of sleeps/loops above but I suppose it could happen. We could search for 'Running|Pending' if that makes sense.
I'm not sure a retry for cancelling will be that helpful here. If the job isn't present in the list as Running, or Pending, it won't need cancelling right?
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username).[BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replaceBEAM-XXXwith the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
Post-Commit Tests Status (on master branch)
Pre-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.