wklken opened a new issue, #9951:
URL: https://github.com/apache/apisix/issues/9951

   ### Current Behavior
   
   register route and service into etcd, the changes not been watched and got 
404
   
   ### Expected Behavior
   
   apisix watch the changes in time, the url should not be 404
   
   ### Error Logs
   
   I have create route/service 4 times, delete the instance and redo
   only 1 time got an error log. another 3 times got no error log(still 404)
   
   
   2023/08/02 08:28:44 [error] 1051#1051: *44434 upstream timed out (110: 
Connection timed out) while reading upstream, client: unix:, server: , request: 
"POST /v3/watch HTTP/1.1", upstream: "http://10.96.15.155:2379/v3/watch";, host: 
"127.0.0.1"
   
   ### Steps to Reproduce
   
   1. upgrade apisix from 3.2.1 to 3.2.2
   2. register the service and route
   3. apisix-dashboard can see the route and service
   4. apisix admin api can fetch the route and service
   5. call the url,  404
   7. do `apisix reload`, call the url, 200;
   8. downgrade to apisix 3.2.1, do 2-5, call the url, 200;
   
   
   ------
   
   got an error log
   
   maybe this feature cause the error: 
https://github.com/apache/apisix/pull/9456
   
   
   
   
   
   
   ### Environment
   
   - APISIX version (run `apisix version`): 3.2.2
   - Operating system (run `uname -a`): 
   - 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`): 2.5.4
   - APISIX Dashboard version, if relevant:
   - 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

Reply via email to