This message originated from Cribl Community Slack.
Click here to view the original link.
Is there an optimal number of REST Collectors to have on a given worker group? We have about 70 on one Worker Group, and are seeing concurrency issues with their executions. I know YMMV depending on how long the API call runs, etc. - but we'd like to plan how we are going to spread them out, and I feel like we'll just end up guessing.
Solved
Cribl Stream: Optimal number of REST Collectors for Worker Group
Best answer by Jon Rust
How are they spaced out?
How long do they run each time?
Are they discover/collect capable, or just a collect?
These things will determine how many workers you need, and if additional WGs would help.
View originalHow many Worker Nodes are in the Group? Are the concurrency limits at their default, or have you already adjusted those settings?
How are they spaced out?
How long do they run each time?
Are they discover/collect capable, or just a collect?
These things will determine how many workers you need, and if additional WGs would help.
Sign up
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.