-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
request help: visit route faster than 1 time/s would return "503 Service Unavailable" #3447
Comments
Is there something interesting in the error.log? You can decrease the log level to info. |
Thanks for the help @spacewander ! I try to visit a route in an interval of 0.1s for 5s, and the whole test (including first set route and one time visit route to make sure it's set) running for ~9s. Out of 50 requests, I got 38 responses, 33 of which are 503, and the rest 5 of them are 200. The info level is a bit messy and I failed to find useful information. I upload them into gist for reference. The |
There is not valuable info in the log... |
Yes a fresh start etcd. Do I need to provide etcd logs? |
If you got time, maybe you could reproduce the error with the chaos test branch. Just start any APISIX instance, comment out the original test (
|
any news? @spacewander |
@membphis spacewander gave me some suggestions to test on slack, but I haven't tested it. It's stuck my side 😬 |
Thanks to @nic-chen, the reason is that I use a dummy but existed URL |
Issue description
In #3404, to test if chaos effect qps of apisix, I try to visit a route in the same frequency, calculate ingress bandwidth per second from prometheus metrics, and then compare before and after the chaos take effect.
The current frequency is 1 time/s, which is pretty slow I think and the reason is that, when frequency is larger than 1 time/s, some visit would return
"503 Service Unavailable"
and the test would fail. The only plugin enabled is prometheus and no request limit related plugins are enabled, so I'm not sure the reason of this.Environment
apisix version
): v2.2uname -a
) Ubuntu 18.04The text was updated successfully, but these errors were encountered: