-
Notifications
You must be signed in to change notification settings - Fork 501
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
Hunts too large for GRPC in master/minion #4004
Comments
It looks like the remote data store rpc is exceeding its size limits - how many hunts do you have? how large are the hunts (types of artifacts - you can see it in the request tab)? how many clients? Try |
Number of hunts varies across the orgs but on average it's 25 and the highest currently is 37 A lot of hunts are single artifacts but payloads are large due to the artifact type, I'm not sure which of those is a factor. An example of a hunt with multiple artifacts is:
There's a single artifact hunt with The largest .db file in datastore/orgs/*/hunts I can find is 2.4MB |
This might be fixed by #4037. This PR gets the minions to refresh hunts directly from the datastore and not use RPC. Also this PR introduces a new parameter API.max_grpc_recv_size which allows the default grpc limit to be increased. Can you please check if the latest CI build works better in your deployment? |
Thanks Mike - I've just tested it and still having issues with the minions crashing out with a timeout. Is Edit: this could be something else as the minion error differs slightly, and hunts in the GUI that were previously too large load correctly now. The new error is just a grpc timeout from the frontend rather than anything specific to hunts. I'll do some more tests and see if I can find anything more useful in the logs. |
Running master/minion config we're getting these errors:
Clients are getting a 502 but the minions do connect and register as frontends with the master.
The text was updated successfully, but these errors were encountered: