heming79 opened a new issue, #7125:
URL: https://github.com/apache/apisix/issues/7125
### Current Behavior
[root@yz-mbg-018203 ~]# curl -voax service-bmlt.wanzhuanmohe.cn -x
192.168.7.204:80
* About to connect() to proxy 192.168.7.204 port 80 (#0)
* Trying 192.168.7.204...
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:--
0* Connected to 192.168.7.204 (192.168.7.204) port 80 (#0)
> GET HTTP://service-bmlt.wanzhuanmohe.cn/ HTTP/1.1
> User-Agent: curl/7.29.0
> Host: service-bmlt.wanzhuanmohe.cn
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 502 Bad Gateway
< Date: Wed, 25 May 2022 04:37:09 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 154
< Connection: keep-alive
< Server: APISIX/2.9
< X-APISIX-Upstream-Status: 502 :
<
{ [data not shown]
100 154 100 154 0 0 15837 0 --:--:-- --:--:-- --:--:--
17111
* Connection #0 to host 192.168.7.204 left intact
去掉问题节点 马上就恢复200状态
[root@yz-mbg-018203 ~]# curl -voax service-bmlt.wanzhuanmohe.cn -x
192.168.7.204:80
* About to connect() to proxy 192.168.7.204 port 80 (#0)
* Trying 192.168.7.204...
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:--
0* Connected to 192.168.7.204 (192.168.7.204) port 80 (#0)
> GET HTTP://service-bmlt.wanzhuanmohe.cn/ HTTP/1.1
> User-Agent: curl/7.29.0
> Host: service-bmlt.wanzhuanmohe.cn
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200
< Content-Type: application/json;charset=utf-8
< Content-Length: 42
< Connection: keep-alive
< Date: Wed, 25 May 2022 04:41:19 GMT
< Server: APISIX/2.9
<
{ [data not shown]
100 42 100 42 0 0 8552 0 --:--:-- --:--:-- --:--:--
10500
### Expected Behavior
只要有一个可用的upstream node ，就应该 返回200 状态 。
nginx就可以 proxy_next_upstream http_404 http_500 http_502 http_503 http_504
error timeout invalid_header;.
应该参考 nginx的 /nstatus 方便运维快速查看、监控所有upstream后端node的 健康状态 。
另外如果 discovery 能支持etcd 要是能像traefik那样 获取k8s的pod地址:端口号 就完美了 。
![Uploading image.png…]()
### Error Logs
我上午起过两个apisix 出现etcd 连接600多个导致 etcd 不可用的情况 。
/usr/local/apisix/logs # tail -f error.log
2022/05/25 02:27:30 [error] 63#63: *304 [lua] config_etcd.lua:563: no
healthy etcd endpoint available, next retry after 2s, context: ngx.timer
2022/05/25 02:27:30 [error] 57#57: *239 [lua] config_etcd.lua:563: no
healthy etcd endpoint available, next retry after 2s, context: ngx.timer
2022/05/25 02:27:31 [error] 50#50: *49 [lua] config_etcd.lua:563: no healthy
etcd endpoint available, next retry after 2s, context: ngx.timer
2022/05/25 02:27:31 [error] 44#44: *77 [lua] config_etcd.lua:563: no healthy
etcd endpoint available, next retry after 4s, context: ngx.timer
不知道什么原因 日志一直在切割归档，而不是zhengd整点才切割归档。
![Uploading image.png…]()
### Steps to Reproduce
1、run apisix docker ， dashboard docker
2、create upstream
3、create route
4、curl -voax service-bmlt.wanzhuanmohe.cn -x 192.168.7.204:80 OK
5、add upstream node （no availabe ）
6、curl -voax service-bmlt.wanzhuanmohe.cn -x 192.168.7.204:80 502
### Environment
- APISIX version (run `apisix version`):2.9
- Operating system (run `uname -a`):centos7.9
- OpenResty / Nginx version (run `openresty -V` or `nginx -V`):1.19.3.1
- etcd version, if relevant (run `curl
http://127.0.0.1:9090/v1/server_info`):3.4.15
- APISIX Dashboard version, if relevant:2.8.0
- Plugin runner version, for issues related to plugin runners:
- LuaRocks version, for installation issues (run `luarocks --version`):3.7.0
--
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: notifications-unsubscr...@apisix.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
