-
Notifications
You must be signed in to change notification settings - Fork 175
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
The --dapr-http-max-request-size flag does not work in InvokeMethodWithContent. #707
Comments
What version of dapr/cli are you using?
|
Thanks, here is my Dapr version::
And I have already set the maximum limit to exceed 4MB in the command line and in the custom-grpc-client.go code,This is my run command, :
This is the error message I get when running the custom-grpc-client above:
It works for So do I have to upgrade to 1.15.0? |
@mikeee Excuse me |
somebody help me. |
Describe the bug
I am using the
examples/service/custom-grpc-client
example, and it seems to work fine withclient.SaveState
. However, when I useInvokeMethodWithContent
to send data larger than 4MB, I still get the error: panic: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (41943086 vs. 4194304). I would like to resolve this issue so thatInvokeMethodWithContent
can send and receive data exceeding 4MB. By the way, the readme suggests using--max-body-size
, but it does not seem to be effective.Below is my modified
custom-grpc-client.go
:I use
dapr run --app-id custom-grpc-client \ -d ./config \ --dapr-http-max-request-size 80 \ --log-level warn \ go run ./custom-grpc-client/main.go
to run itTo Reproduce
Expected behavior
I hope to be able to send and receive larger data using InvokeMethodWithContent.
The text was updated successfully, but these errors were encountered: