jinjianming opened a new issue, #485:
URL: https://github.com/apache/apisix-helm-chart/issues/485
### Description
1. At present, I have learned about the coupling architecture through the
K8S deployment. When I restart the POD, the data plane service cannot update
the latest address, resulting in the request for 502 bad gateway
Discovery ` sync_ Data() res: null ` res result is null and the update
failed
```
2023/02/27 04:11:20 [info] 50#50: *381 [lua] resolver.lua:88:
parse_domain(): dns resolver domain: apisix-control-plane-control-plane to
10.233.46.87, context: ngx.timer
2023/02/27 04:11:20 [info] 50#50: *383 [lua] v3.lua:852: request_chunk():
http request method: POST path: /watch body:
{"create_request":{"key":"L2FwaXNpeC91cHN0cmVhbXM=","range_end":"L2FwaXNpeC91cHN0cmVhbXQ=","start_revision":47}}
query: nil, context: ngx.timer
2023/02/27 04:11:20 [info] 50#50: *383 [lua] config_etcd.lua:392:
sync_data(): waitdir key: /apisix/upstreams prev_index: 47, context: ngx.timer
2023/02/27 04:11:20 [info] 50#50: *383 [lua] config_etcd.lua:393:
`sync_data(): res: null`, err: timeout, context: ngx.timer
2023/02/27 04:11:20 [info] 50#50: *383 [lua] v3.lua:76: choose_endpoint():
choose endpoint: https://apisix-control-plane-control-plane:9280, context:
ngx.timer
2023/02/27 04:11:20 [info] 50#50: *383 [lua] client.lua:123: dns_parse():
dns resolve apisix-control-plane-control-plane, result:
{"name":"apisix-control-plane-control-plane.ingress-apisix.svc.cluster.local","type":1,"class":1,"address":"10.233.46.87","ttl":30,"section":1},
context: ngx.timer
2023/02/27 04:11:20 [info] 50#50: *383 [lua] resolver.lua:84:
parse_domain(): parse addr:
{"name":"apisix-control-plane-control-plane.ingress-apisix.svc.cluster.local","type":1,"class":1,"section":1,"ttl":30,"address":"10.233.46.87"},
context: ngx.timer
2023/02/27 04:11:20 [info] 50#50: *383 [lua] resolver.lua:85:
parse_domain(): resolver: ["169.254.25.10"], context: ngx.timer
2023/02/27 04:11:20 [info] 50#50: *383 [lua] resolver.lua:86:
parse_domain(): host: apisix-control-plane-control-plane, context: ngx.timer
```
2. The requested address is still the old one
```
2023/02/27 04:23:28 [error] 54#54: *20479 connect() failed (111: Connection
refused) while connecting to upstream, client: 192.168.0.48, server: _,
request: "GET / HTTP/1.1", upstream: "http://10.233.64.11:80/";, host:
"cjyoumen.com"
```
3. I can see from the dashboard that upstream is up to date, and Data-plane
cannot automatically refresh the latest address;
### Environment
- APISIX version (run `apisix version`): 3.1.0
- Operating system (run `uname -a`): 4.15.0-202-generic Ubuntu SMP Thu Jan 5
19:19:12 UTC 2023 x86_64 GNU/Linux
- OpenResty / Nginx version (run `openresty -V` or `nginx -V`): nginx
version: openresty/1.21.4.1
- etcd version, if relevant (run `curl
http://127.0.0.1:9090/v1/server_info`):
{"etcdserver":"3.5.4","etcdcluster":"3.5.0"}
- APISIX Dashboard version, if relevant: 3.0.0-alpine
- Plugin runner version, for issues related to plugin runners:
- LuaRocks version, for installation issues (run `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]
