jinjianming opened a new issue, #484: URL: https://github.com/apache/apisix-helm-chart/issues/484
Description 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 I checked the data-plane logs and found that the synchronization of control-plane data was timed out, but I manually tested "curl https://apisix-control-plane-control-plane:9280/version "Is able to return results; My Error Logļ¼ 2023/02/27 01:51:14 [info] 89#89: *452 [lua] config_etcd.lua:392: sync_data(): waitdir key: /apisix/upstreams prev_index: 2132, context: ngx.timer 2023/02/27 01:51:14 [info] 89#89: *452 [lua] config_etcd.lua:393: sync_data(): res: null, err: timeout, context: ngx.timer Environment APISIX version (run apisix version): 3.1.0 Operating system (run uname -a): 4.15.0-202-generic https://github.com/apache/apisix/issues/213-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: notifications-unsubscr...@apisix.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
