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

pubsub: gRPC max recv set to 4MB #2190

Closed
chrisgoffinet opened this issue Apr 7, 2017 · 7 comments
Closed

pubsub: gRPC max recv set to 4MB #2190

chrisgoffinet opened this issue Apr 7, 2017 · 7 comments
Assignees
Labels
api: pubsub Issues related to the Pub/Sub API. core priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@chrisgoffinet
Copy link

chrisgoffinet commented Apr 7, 2017

Reproduce steps:

@google-cloud/pubsub: 0.3.0 0.9.0
Publish message > 4MB to a topic
Retrieve message through subscription: Error: Received message larger than max (6374241 vs. 4194304)

#2007 was pushed to fix the limits but the existing PubSub client seems to be still defaulting to 4MB. It was originally posted about on #1991 which was closed after #2007 was merged but still throwing that error.

@stephenplusplus
Copy link
Contributor

That module is on version 0.9.0 now. Can you try upgrading?

@stephenplusplus stephenplusplus added the api: pubsub Issues related to the Pub/Sub API. label Apr 7, 2017
@lukesneeringer lukesneeringer added type: question Request for information or clarification. Not an issue. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Apr 7, 2017
@chrisgoffinet
Copy link
Author

I made a typo when filling out this ticket, I am on version 0.9.0 not 0.3.0. So it's still failing there.

@chrisgoffinet
Copy link
Author

Also confirmed by looking at node_modules, I see the change made on the gRPC side common-grpc/src/service.js, so it's definitely pulled in. Could this be an issue on PubSub server side?

@stephenplusplus
Copy link
Contributor

Thanks for confirming.

@murgatroid99 I tried to remove the message limit with the changes in this PR: #2007 -- did I make a mistake, or could this error be coming from the API response?

@murgatroid99
Copy link

The options that you add in that PR are gRPC Client constructor arguments. They are supposed to be in the same object as the 'grpc.primary_user_agent' on line 802 of service.js.

@stephenplusplus stephenplusplus self-assigned this Apr 7, 2017
@stephenplusplus
Copy link
Contributor

Gotcha, thanks!

@stephenplusplus stephenplusplus added core type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. and removed type: question Request for information or clarification. Not an issue. labels Apr 7, 2017
@stephenplusplus
Copy link
Contributor

PR sent with a fix in #2192 -- good catch @chrisgoffinet!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: pubsub Issues related to the Pub/Sub API. core priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

4 participants