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

self.locust.drop_current_runner() #802

Closed
styk-tv opened this issue May 23, 2018 · 1 comment
Closed

self.locust.drop_current_runner() #802

styk-tv opened this issue May 23, 2018 · 1 comment

Comments

@styk-tv
Copy link

styk-tv commented May 23, 2018

i use locust for distributing a large test across several thousands of workers. there is a precise number of hits every worker is supposed to make. basically a data list of requests picked up from kafka and distributed to all the workers. after all workers exhaust all the lists i want to be able to start dropping workers. all the way to zero after last message has been sent.

i know many people have asked about this for the past 5 years. i love the framework but this for me is difficult to deal with. is there a way to overwrite continuous behaviour and terminate worker when tasks are completed?

@styk-tv styk-tv changed the title if task completed, drop worker self.locust.drop_worker() May 23, 2018
@styk-tv styk-tv changed the title self.locust.drop_worker() self.locust.drop_current_runner() May 23, 2018
@cgoldberg
Copy link
Member

can't you already do this using on_stop() or teardowns?
https://docs.locust.io/en/latest/writing-a-locustfile.html#the-on-start-and-on-stop-methods

i know many people have asked about this for the past 5 years.

This project is developed and maintained by volunteers... Asking about a feature for 5 years doesn't magically implement it. Someone has to actually volunteer and write code.

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

No branches or pull requests

2 participants