-
Notifications
You must be signed in to change notification settings - Fork 185
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
Error, message length too large: found 7666438 bytes, the limit is: 4194304 bytes #773
Comments
Hi @andygrove, we also meet the same issue. I will propose a PR to add a config to make the maximum decoded message size configurable for temporary fix. |
I am still running into this error with the latest code.
I am using the default |
We currently set the decoding max size but not the encoding max size, so perhaps that is the issue. I will test this. |
We've hit some other errors related to max sizes at our end (Coralogix), we reduced those errors by:
|
Some other things we did:
|
I confirmed that setting the max encoding size resolves the issue for me. |
We set max encode/decode message size when creating the gRPC servers, but not for the clients, so I ran into this again. |
Describe the bug
I tried running some benchmarks, but some queries fail with this error:
To Reproduce
Start cluster:
Run TPC-H benchmarks
Expected behavior
Should not fail
Additional context
The text was updated successfully, but these errors were encountered: