Skip to content
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

increase grpc recv limit #20906

Merged
merged 2 commits into from
Apr 2, 2019
Merged

increase grpc recv limit #20906

merged 2 commits into from
Apr 2, 2019

Conversation

jbardin
Copy link
Member

@jbardin jbardin commented Apr 2, 2019

Some providers may generate quite large schemas, and the internal
default grpc response size limit is 4MB. 64MB should cover most any use
case, and if we get providers nearing that we may want to consider a
finer-grained API to fetch individual resource schemas.

Fixes #20879

@jbardin jbardin requested a review from a team April 2, 2019 19:46
// if we get providers nearing that we may want to consider a finer-grained
// API to fetch individual resource schemas.
const maxRecvSize = 64 << 20
protoResp, err := p.client.GetSchema(p.ctx, new(proto.GetProviderSchema_Request), grpc.MaxRecvMsgSizeCallOption{MaxRecvMsgSize: maxRecvSize})
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should mention in the comment above that this is an experimental setting, as an aid to the hypothetical future developer that upgrades the grpc dependency and suddenly sees a build error reported from this location.

Some providers may generate quite large schemas, and the internal
default grpc response size limit is 4MB. 64MB should cover most any use
case, and if we get providers nearing that we may want to consider a
finer-grained API to fetch individual resource schemas.
@jbardin jbardin force-pushed the jbardin/grpc-recv-limit branch from 4ec5138 to 746aac8 Compare April 2, 2019 19:53
@jbardin jbardin merged commit 7ced464 into master Apr 2, 2019
@jbardin jbardin deleted the jbardin/grpc-recv-limit branch April 2, 2019 20:46
@pawelsocha
Copy link

pawelsocha commented Jul 4, 2019

Whats about plugin/grpc_provisioner.go?
in p.client.GetSchema variable MaxRecvMsgSize also should be set?

@ghost
Copy link

ghost commented Jul 24, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Jul 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

grpc: received message larger than max
3 participants