Repository navigation
gRPC max size limit #1991
Description
Activity
@murgatroid99 @jmuk do you know if there's a way to handle this?
It's really obscure to me how to customize the parameters like this. Maybe the third parameter to the Client constructor might be used (https://github.com/grpc/grpc/blob/master/src/node/src/client.js#L732) but I don't know what values or structures can configure this.
@murgatroid99, do you know which keys/values we should use here?
The keys and values are defined at https://github.com/grpc/grpc/blob/master/include/grpc/impl/codegen/grpc_types.h#L148. The one you want for this case is
"grpc.max_send_message_length".Reacted by Hangchen YU, Konstantin Sokolovskii, Vinllen and RWThanks!
I also filed googleapis/gax-nodejs#107 for this problem.
PR sent to remove the limit of the max message sent length and max message received length: #2007
- added 2 commits that reference this issue
on Feb 21, 2017 We still seem to be hitting this 4mb limit while testing with the following versions:
"@google-cloud/bigtable": "0.10.1", "@google-cloud/pubsub": "0.11.0", "@google-cloud/storage": "1.1.0"Any recommendation for how to avoid this GRPC limit?
I am using the grpcio python lib, and encounter the same issue, any idea to get rid of this?
- added a commit that references this issue
on Jul 23, 2025 - added a commit that references this issue
on Oct 22, 2025 - added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Mar 11, 2026
Since grpc version 1.0.0, message size is limit 4MB, and pubsub itself supports payload size upto 10MB. If there is message that is greater than 4MB in queue, pubsub client errors out with
Error: Received message larger than max (6374241 vs. 4194304)Environment details
Steps to reproduce
Thanks!