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

grpc: received message larger than max #3955

Closed
lukerosser opened this issue Dec 9, 2024 · 3 comments
Closed

grpc: received message larger than max #3955

lukerosser opened this issue Dec 9, 2024 · 3 comments

Comments

@lukerosser
Copy link

Version: 4a41ec1

We're getting this error on a single hunt:

Error: grpc: received message larger than max (4423416 vs. 4194304)

Request URL: https://velociraptor/api/v1/GetHunt?hunt_id=H.CT31LC0KI2DVI
Request Method: GET
Status Code: 429 Too Many Requests
@scudette
Copy link
Contributor

scudette commented Dec 9, 2024

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.

@lukerosser
Copy link
Author

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!

@scudette
Copy link
Contributor

scudette commented Dec 9, 2024

Should be fixed by #3957

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

2 participants