-
Notifications
You must be signed in to change notification settings - Fork 179
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
[Access] Update default grpc max message size to 1GiB #4609
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4609 +/- ##
==========================================
+ Coverage 54.63% 54.67% +0.03%
==========================================
Files 915 915
Lines 85445 85445
==========================================
+ Hits 46687 46716 +29
+ Misses 35170 35141 -29
Partials 3588 3588
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
do clients also need to be updated?
It wouldn't hurt, but it's only needed if they are using this setting directly from |
bors merge |
4609: [Access] Update default grpc max message size to 1GiB r=peterargue a=peterargue Closes: #4596 The amount of data returned from some Access API requests has increased over time, resulting in response size errors on Access and Execution nodes. While the max message size is configurable via CLI flags, this PR updates the default to be well above the current largest messages. Co-authored-by: Peter Argue <89119817+peterargue@users.noreply.github.com>
Build failed: |
Closes: #4596
The amount of data returned from some Access API requests has increased over time, resulting in response size errors on Access and Execution nodes. While the max message size is configurable via CLI flags, this PR updates the default to be well above the current largest messages.