-
Notifications
You must be signed in to change notification settings - Fork 3k
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
cannot specify task of UserClass when locust run on distributed mode #2657
Comments
huh. good find. unfortunately it will probably be hard to support, so I'll probably "fix" it by throwing an error (at least for now) |
I guess the reason it's hard to support is that in distributed mode, there's no shared data strategy. The single-process mode uses memory, while distributed mode would require introducing Redis or other memory database. |
Actually. When I think about it, it should work. Not sure when I'll have time to look at it though... |
It would be the same for distributed mode, we need to communicate between the workers and the master node so that the workers know that the list of tasks has changed. @cyberw Perhaps in the meantime we should throw an error or note something in the documentation that these arguments don't work together yet |
We shouldnt really have options that only work with non-distributed so we need to try and solve it (or remove task selection entirely). But erroring out when combined with --processes or --master is better than the current state I guess :) |
Prerequisites
Description
if launch locust with
--processes
argument, choosing task will not working.Command line
locust --processes 2 --class-picker -f locustfiles
Locustfile contents
Python version
3.12
Locust version
2.24
Operating system
macOS or centOS
The text was updated successfully, but these errors were encountered: