hansedong commented on issue #9336: URL: https://github.com/apache/apisix/issues/9336#issuecomment-1552739853
> > When I switched the `deployment.etcd.timeout` from `120` to `30`, the error disappeared. > > And if I change it back to `120`, the timeout error logs showed up 100% after reloading. > > ``` > 2023/05/18 08:10:58 [error] 837#837: *59888 upstream timed out (110: Connection timed out) while reading upstream, client: unix:, server: , request: "POST /v3/watch HTTP/1.1", upstream: "http://x.x.x.x:2379/v3/watch";, host: "127.0.0.1" > 2023/05/18 08:10:58 [error] 841#841: *59837 [lua] config_etcd.lua:634: failed to fetch data from etcd: closed, etcd key: /bk-gateway-0-apisix/global_rules, context: ngx.timer > ``` @wklken "Yes, it's the same as my situation." > In fact, the timeout error logs are expected. > Since apisix 2.15, the connection between apisix and etcd is proxied via an internal conf server, which uses nginx upstream but not resty cosocket to connect etcd. It's configured with a timeout value, when it timed out, the nginx will close the connection on its own and print log. @kingluo what is the timeout value used by the internal conf server to connect to Etcd? -- 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]
