zuiyangqingzhou opened a new issue #4528: URL: https://github.com/apache/apisix/issues/4528
### Issue description first： > > https://github.com/apache/apisix/blob/cb8e41d5f4037c332978dc21eff7a63e0ab48322/apisix/schema_def.lua#L136 > > Regarding this timeout, I understand that it is the timeout period of the upstream health check. If the upstream does not respond after this time, it may be marked as a suspected unhealthy node second: > > https://github.com/apache/apisix/blob/cb8e41d5f4037c332978dc21eff7a63e0ab48322/apisix/schema_def.lua#L146-L167 > > Regarding this code, what I understand is that there can be independent health check intervals for healthy upstream. If several consecutive cycles (depending on the number of successful configurations) are OK, it is considered a healthy node, otherwise it is considered to be a Unhealthy node third: > > https://github.com/apache/apisix/blob/cb8e41d5f4037c332978dc21eff7a63e0ab48322/apisix/schema_def.lua#L172-L202 > I understand that the interval time here is to control the interval time for detecting unhealthy nodes, but there is a timeout parameter here. What is the difference between this timeout time and the timeout time of the first code snippet? Is my understanding of the three code snippets correct? What is the difference between the timeout parameter in the first and third paragraphs? ### Environment Request help without environment information will be ignored or closed. * apisix version (cmd: `apisix version`): * OS (cmd: `uname -a`): * OpenResty / Nginx version (cmd: `nginx -V` or `openresty -V`): * etcd version, if have (cmd: run `curl http://127.0.0.1:9090/v1/server_info` to get the info from server-info API): * apisix-dashboard version, if have: * luarocks version, if the issue is about installation (cmd: `luarocks --version`): -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
