hanzhenfang commented on issue #12832:
URL: https://github.com/apache/apisix/issues/12832#issuecomment-6572368849

   Hi @idb-root, I’d like to follow up on this issue. Could you please share a 
few more details to help us narrow down where the timeout occurs?
   
   1. **Pod details and logs:** Is the issue still reproducible? Which nodes 
are the affected and working APISIX Pods running on? Please also share the 
affected Pod’s startup logs, including the previous container logs:
   
      ```bash
      kubectl logs <affected-pod> -c apisix --previous
      ```
   
   2. **Connectivity from the affected Pod:** Could you test 
`http://apisix-etcd:2379/version` and a `POST` to `/v3/kv/put` from the 
affected Pod’s network environment, and share the results and request 
durations? If the container restarts too quickly, a debug container attached to 
the same Pod may help. Please use an authorized test key outside the APISIX 
configuration prefix.
   
   3. **Configuration and image:** Please share the relevant parts of 
`config.yaml`, with credentials and sensitive values redacted, and confirm the 
actual image digest and APISIX version. The Deployment label shows `3.2.0`, 
while the image tag is `3.14.1-debian`.
   
   4. **Custom Lua file:** Could you provide more details about the file 
mounted under `/usr/local/openresty/lualib/resty/`? Does it replace a file 
already present in the image?
   
   5. **etcd health:** What etcd version and topology are you using? Were there 
any slow requests or relevant etcd logs around the time of the failure?
   
   Thank you!
   


-- 
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]

Reply via email to