jujiale commented on issue #9847:
URL: https://github.com/apache/apisix/issues/9847#issuecomment-2209119803
> @ShuLian1984 Is there any error log like `failed to create etcd instance
for fetching /routes` when your APISIX restarts? Or any other log at the start
of the restart? Can you check if there are active connections to etcd,
specifically on the `/apisix/routes` when the container restarts? And just to
confirm, when you reapply the routes, it works again, right?
@ShuLian1984 hello, we suffered such a situation as you metioned above, when
we use apisix-dashboard modify the route config, we found that in etcd, the
config is the same as we modified（and the update_time is correct）, but when I
invoke /v1/route/{route id}， it is old config, and the update_time is very
long before since I modified recently， error log like below:
`
2024/07/04 16:00:55 [error] 16235#16235: *143280176 [lua]
config_util.lua:86: failed to find clean_handler with idx 1, client:
172.24.61.47, server: _, request: "POST /xxxxx/epl HTTP/1.1", host: "xxxxx"
2024/07/04 16:00:55 [error] 16240#16240: *143284010 [lua]
config_etcd.lua:584: failed to fetch data from etcd:
/usr/local/apisix/core/config_util.lua:104: attempt to index local 'item' (a
boolean value)
stack traceback:
/usr/local/apisix/core/config_util.lua:104: in function
'fire_all_clean_handlers'
/usr/local/apisix/core/config_etcd.lua:315: in function 'sync_data'
/usr/local/apisix/core/config_etcd.lua:541: in function
</usr/local/apisix/core/config_etcd.lua:532>
[C]: in function 'xpcall'
/usr/local/apisix/core/config_etcd.lua:532: in function
</usr/local/apisix/core/config_etcd.lua:513>, etcd key: /test1/apisix/routes,
context: ngx.timer
`
I want to know why such situation could happen, and if community has
resolved it, thanks
use apisix 2.15.0 etcd 3.5.0
--
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]
