-
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
Stop locusts graceful #1062
Comments
Hi. Try using |
|
Not sure if I got it correctly, but task teardown only happens after |
|
Nice to know that. I'm sorry that won't help you. |
I'm trying to add this feature in #1099 . I just need to fix my bugs first :) |
Awesome news! ;) |
Cool, I'll have a look at that! |
Oops, wrong button - I have been closing too many tickets :) |
Proposal
Add possibility to stop locusts without killing them (via
Greenlet.kill
). Currently executed tasks should continue, but no new tasks should be scheduled.Motivation
My load test is a bit uncommon, since I'm using some prepopulation and an additional utility database (redis), which data should be consistent with application data. So my locustfile contains something like this:
When I press [Stop] button, a few on-the-fly tasks are interrupted between (1) and (2). Unfortunately this means that data between application and redis become inconsistent and I'm no longer able to restart test. It forces me to start my prepopulation script again and waste a lot of time.
If locust tasks were stopped graceful, allowing them to return, there would be no problem.
The text was updated successfully, but these errors were encountered: