We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/apache/incubator-apisix/blob/82f85e59465c80e27879d9985461d60fe4f77721/apisix/balancer.lua#L254-L269
Currently we only report the HTTP status in the test next stage. However, only unhealthy upstream will trigger a test next try. Does the passive health check make any report when an unhealthy upstream goes healthy? Does the healthy part of the passive health configuration work as expected? https://github.com/apache/incubator-apisix/blob/82f85e59465c80e27879d9985461d60fe4f77721/apisix/schema_def.lua#L159
test next
healthy
passive
The text was updated successfully, but these errors were encountered:
I think we can fix it in the log phase.
Sorry, something went wrong.
bugfix: passive health check seems never provide a healthy report (#1918
2ba0231
) Fix #1640
membphis
Successfully merging a pull request may close this issue.
https://github.com/apache/incubator-apisix/blob/82f85e59465c80e27879d9985461d60fe4f77721/apisix/balancer.lua#L254-L269
Currently we only report the HTTP status in the
test next
stage. However, only unhealthy upstream will trigger atest next
try. Does the passive health check make any report when an unhealthy upstream goes healthy? Does thehealthy
part of thepassive
health configuration work as expected?https://github.com/apache/incubator-apisix/blob/82f85e59465c80e27879d9985461d60fe4f77721/apisix/schema_def.lua#L159
The text was updated successfully, but these errors were encountered: