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

MAX_MESSAGE_SIZE clarification for Clients #2175

Open
mgrazianoc opened this issue Feb 5, 2025 · 0 comments
Open

MAX_MESSAGE_SIZE clarification for Clients #2175

mgrazianoc opened this issue Feb 5, 2025 · 0 comments

Comments

@mgrazianoc
Copy link

According to the official documentation on version 0.12.3, is states:

Currently, both servers and clients can be configured to set the max message encoding and decoding size. This will ensure that an incoming gRPC message will not exhaust the systems memory. By default, the decoding message limit is 4MB and the encoding limit is usize::MAX.

On the server side, we can configure these limits directly within the service, using max_decoding_message_size and max_encoding_message_size.

However, I don’t see any documented examples of how to configure these limits for the client side, nor can I find any references in the source code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant