cannot specify task of UserClass when locust run on distributed mode about locust HOT 5 CLOSED

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 :)

from locust.

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)

from locust.

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.

from locust.

Actually. When I think about it, it should work. Not sure when I'll have time to look at it though...

from locust.

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

from locust.