-
Notifications
You must be signed in to change notification settings - Fork 9.9k
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
Is there a way to configure grpc.MaxCallRecvMsgSize #12576
Comments
@spacewander Should this not be a gRPC Gateway question? I believe gRPC Gateway may be providing this kind of capability through metadata sent as part of request header. |
@agargi |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions. |
Does the problem still exist? |
@spacewander Our apisix use etcd v3.4, still exist. |
Ensure the client which access etcd via grpc-gateway won't be limited by the MaxCallRecvMsgSize. Here we choose the same default value of etcdcli as grpc-gateway's MaxCallRecvMsgSize. Fix etcd-io#12576
@simonhou |
Ensure the client which access etcd via grpc-gateway won't be limited by the MaxCallRecvMsgSize. Here we choose the same default value of etcdcli as grpc-gateway's MaxCallRecvMsgSize. Fix etcd-io#12576
Ensure the client which access etcd via grpc-gateway won't be limited by the MaxCallRecvMsgSize. Here we choose the same default value of etcdcli as grpc-gateway's MaxCallRecvMsgSize. Fix etcd-io#12576
Ensure the client which access etcd via grpc-gateway won't be limited by the MaxCallRecvMsgSize. Here we choose the same default value of etcdcli as grpc-gateway's MaxCallRecvMsgSize. Fix etcd-io#12576
Ensure the client which access etcd via grpc-gateway won't be limited by the MaxCallRecvMsgSize. Here we choose the same default value of etcdcli as grpc-gateway's MaxCallRecvMsgSize. Fix etcd-io#12576
Ensure the client which access etcd via grpc-gateway won't be limited by the MaxCallRecvMsgSize. Here we choose the same default value of etcdcli as grpc-gateway's MaxCallRecvMsgSize. Fix etcd-io#12576
Ensure the client which access etcd via grpc-gateway won't be limited by the MaxCallRecvMsgSize. Here we choose the same default value of etcdcli as grpc-gateway's MaxCallRecvMsgSize. Fix etcd-io#12576
After #9043, the grpc client can set MaxCallRecvMsgSize when creating a request.
But when the client accesses etcd via http (through the proxy of grpc-gateway), it seems there is not a way to configure
grpc.MaxCallRecvMsgSize
?The text was updated successfully, but these errors were encountered: