Uh oh!
There was an error while loading. Please reload this page.
[BEAM-12448] Relax ping limits on the gRPC server - #15314
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.
|
tvalentyn
commented
Aug 31, 2021
hi @angoenka - could you please take a look at this change? |
aaltay
commented
Aug 31, 2021
I missed this review request earlier. Sorry for the delay and thank you for the contribution. |
ibzib
commented
Sep 10, 2021
R: @ibzib |
stefanistrate
commented
Oct 5, 2021
I've just run |
tvalentyn
commented
Oct 5, 2021
perhaps it's a flake, let's retry. |
tvalentyn
commented
Oct 5, 2021
Run Portable_Python PreCommit |
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.