Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Is it possible to autoscale slaves?

See original GitHub issue

For example when running on Kubernetes this is very easy to set up by adding a HorizontalPodAutoscaler but will locust be OK with new slaves connecting to the master as the users are increased?

Issue Analytics

State:
Created 4 years ago
Comments:12 (10 by maintainers)

Top GitHub Comments

2reactions

heymancommented, Nov 13, 2019

@max-rocket-internet The master will send out new hatch messages to the slave nodes. Which will result in the existing 10 nodes killing ~90 of their running locust users, and the new node spawning ~900 users.

A bug was causing a temporary drop in the current RPS when this happened, as reported by #1143, but that has now been fixed in master.

2reactions

max-rocket-internetcommented, Aug 27, 2019

@cgoldberg @aldenpeterson-wf

Would you not consider using issue labels like many other repos? I understand you don’t want to provide user support, and that’s totally fine, but as you can see most people view Github issues for a project as a go to place for users as well as developers. With labels and filtering you can support both without too much headache 😅

Pushing people to Slack is easy but it’s so ephemeral, even for the people that do go to the effort of creating an account.