-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Time response graph is not working on master/slave configuration #1182
Comments
This was fixed in 0.13.2 (https://github.com/locustio/locust/blob/master/CHANGELOG.md#0132). |
We still get this issue with 0.14.x Locust... Charts goes off after sometimes |
@abinjaik: I'm not able to reproduce your issue. Feel free to open a new ticket with as much information as possible on how to reproduce the issue. And if possible provide us with a minimal reproducible code example. |
Yes, I am having locust 0.14/latest, running on 8 core , 16 GB Linux Master
and running 6-7 slaves each on 2 of the other machines with similar
configuration. Yes, we run slaves on the same machine of Master as well -
assume that's fine. After certain load the charts tab, slaves tab and R/s
etc on the locust dashboard shows empty - no data. We tried using Chrome
and Firefox on the same machine , also tried the ip-port http url from
other machines, everywhere we have this issue
…On Sat, Feb 29, 2020, 2:45 AM Jonatan Heyman, ***@***.***> wrote:
@abinjaik <https://github.com/abinjaik>:
I don't think you're experiencing a regression of this issue, since this
bug was only for the response time graph, and if I understand you
<#1263 (comment)>
correctly all graphs stops working?
I'm not able to reproduce your issue. Feel free to open a new ticket with
as much information as possible on how to reproduce the issue. And if
possible provide us with a minimal reproducible code example.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1182?email_source=notifications&email_token=AGI5YFINDQA3I3FPHGJ6Y23RFDTODA5CNFSM4JTUDIZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENLWW2A#issuecomment-592931688>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGI5YFIKKJYC3GLT7PW3AC3RFDTODANCNFSM4JTUDIZA>
.
|
When this happens do you see any errors in the browser/javascript console? What happens if you reload the page? How is the CPU usage of the master? For me to be able to help you I really need a way to reproduce the issue. |
EDIT: posting in new issue instead: #1276 |
After migrating to last python and locust releases and running a master-slave configuration in docker (one container for each master-slave node), the time response graph is not working: "No data" is showing by move pointer to the response-time line (see attached images).
NOTE: Download data function is working well
Expected behaviour
Time response graph should display all average response time distribution for the current execution
Actual behaviour
After some seconds average response time goto "No data", Clicking on reset stats, the data return for 2-3 seconds and again drop to 0. The behaviours cannot be reproduced on a single container execution (without master/slaves):
Steps to reproduce
Update locust and python to last releases and rerun the cluster
Environment settings
Locust version: 0.13.1
Python/alpine version: python:3.8.0-alpine3.10
docker version:17.05.0-ce running on debian 9
The text was updated successfully, but these errors were encountered: