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

--stop-timeout is not respected when changing number of running Users in distributed mode #1162

heyman opened this issue Nov 19, 2019 · 0 comments


Copy link

@heyman heyman commented Nov 19, 2019

Describe the bug

When running Locust distributed, and changing the number of simulated Users (e.g. if a new slave node connects), simulated users will be killed immediately without respecting --stop-timeout

Expected behavior

Running locust user should get a chance to finish their tasks within the specified stop-timeout.

Actual behavior

Running locust users are killed immediately.


I'm currently working on a fix for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant