-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[BEAM-12448] Relax ping limits on the gRPC server #15314
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
Codecov Report
@@ Coverage Diff @@
## master #15314 +/- ##
==========================================
- Coverage 83.81% 83.80% -0.01%
==========================================
Files 441 444 +3
Lines 59745 60477 +732
==========================================
+ Hits 50075 50683 +608
- Misses 9670 9794 +124
Continue to review full report at Codecov.
|
|
hi @angoenka - could you please take a look at this change? |
|
I missed this review request earlier. Sorry for the delay and thank you for the contribution. |
|
R: @ibzib |
|
I've just run |
perhaps it's a flake, let's retry. |
|
Run Portable_Python PreCommit |
ibzib
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
R: @aaltay
I find myself running longer jobs locally via the DirectRunner and I keep getting errors like this:
I understand that the DirectRunner has its limitations and, in my case, I'm not using it for production jobs. However, it would be nice if some of the ping limits are relaxed a bit. Currently, the gRPC server has fairly strict limits:
My PR removes these 2 limits completely wherever
grpc.server()is invoked (Python SDK only). I'm not sure this is the best approach, but I'm happy to adjust it based on your feedback.Bonus request: it would be even nicer if Beam could allow passing options to the gRPC client & server via some flags.
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.
ValidatesRunnercompliance status (on master branch)Examples testing status on various runners
Post-Commit SDK/Transform Integration 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.