-
Notifications
You must be signed in to change notification settings - Fork 503
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
grpc: received message larger than max #3955
Comments
This is similar to #3780 (Remove compiled collector args for HuntList response so it can fit within the gRPC size limit.) but while in that PR the reason the response size overflowed if because the entire listing included the compiled collector args for each hunt in the table, in this case this retrieves only a single hunt. If the compiled collector arg overflows the response size with a single hunt, that means the hunt is absolutely massive. It is probably not a great idea to send such a large request to each hunt as it will lead to a lot of network traffic and use up a lot of server resources. What kind of hunt is it? is it a single hunt collecting a lot of artifacts or one artifact with a lot of data in it? We can implement a similar solution to #3780 but we have to load the compiled args for the request tab because the user needs to be able to see the full request we sent to the client. |
It's a single hunt with a lot of artifacts if I remember right. As you say we might reconsider running it as one hunt but if there's a solution for this error too that'd be great, thanks! |
Should be fixed by #3957 |
Version: 4a41ec1
We're getting this error on a single hunt:
Error: grpc: received message larger than max (4423416 vs. 4194304)
The text was updated successfully, but these errors were encountered: