1473371932 opened a new issue, #10756: URL: https://github.com/apache/apisix/issues/10756
### Current Behavior Hi, may I ask where are the routing rules set in APISIX stored? I found that after the routing rules are configured for a while, they disappear. However, after checking, my APISIX related pods did not restart，what could be the reason for this? I'm not sure exactly when it happens, but it happens every time This morning, when I checked the routing configuration, I found that the configured plugins in APISIX had disappeared, but I am certain that the APISIX-related Pods have not restarted ``` root@k8s-master:~# root@k8s-master:~# curl -s http://10.109.77.186:9180/apisix/admin/routes/d60675a2 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' | jq { "createdIndex": 996, "value": { "desc": "Created by apisix-ingress-controller, DO NOT modify it manually", "id": "d60675a2", "name": "deepflow-otel-spring-demo_deepflow-otel-spring-demo_deepflow-otel-spring-demo", "status": 1, "create_time": 1704249167, "labels": { "managed-by": "apisix-ingress-controller" }, "uris": [ "/*" ], "update_time": 1704416537, "hosts": [ "apisix.deepflow.demo.com" ], "upstream_id": "36119e76", "priority": 0 }, "key": "/apisix/routes/d60675a2", "modifiedIndex": 1630 } root@k8s-master:~# root@k8s-master:~# kubectl get pods -n apisix -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES apisix-7b4d48bf46-2dqvw 1/1 Running 0 21h 10.244.235.211 k8s-master <none> <none> apisix-dashboard-fd4f97c8c-zdp2k 1/1 Running 0 2d18h 10.244.235.197 k8s-master <none> <none> apisix-etcd-0 1/1 Running 1 (8d ago) 9d 10.244.235.196 k8s-master <none> <none> apisix-ingress-controller-5dbdb8c8d8-zhp7q 1/1 Running 1 (8d ago) 9d 10.244.235.194 k8s-master <none> <none> root@k8s-master:~# ``` Then, I re-added the configuration that had disappeared，And there is indeed no problem with the verification： ``` root@k8s-master:~# curl http://10.109.77.186:9180/apisix/admin/routes/d60675a2 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d ' > { > "name": "deepflow-otel-spring-demo", > "methods": ["GET"], > "uris": ["/*"], > "plugins": { > "prometheus":{ > "prefer_name": true > }, > "opentelemetry": { > "sampler": { > "name": "always_on" > }, > "additional_attributes": [ > "deepflow=demo" > ] > } > }, > "upstream": { > "type": "roundrobin", > "nodes": { > "10.1.23.200:18090": 1 > } > } > }' {"key":"/apisix/routes/d60675a2","value":{"priority":0,"id":"d60675a2","name":"deepflow-otel-spring-demo","status":1,"uris":["/*"],"upstream":{"type":"roundrobin","nodes":{"10.1.23.200:18090":1},"pass_host":"pass","scheme":"http","hash_on":"vars"},"methods":["GET"],"plugins":{"prometheus":{"prefer_name":true},"opentelemetry":{"sampler":{"name":"always_on","options":{"root":{"name":"always_off"},"fraction":0}},"additional_attributes":["deepflow=demo"]}},"create_time":1704249167,"update_time":1704418883}} root@k8s-master:~# root@k8s-master:~# curl -s http://10.109.77.186:9180/apisix/admin/routes/d60675a2 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' | jq { "createdIndex": 996, "value": { "priority": 0, "id": "d60675a2", "name": "deepflow-otel-spring-demo", "status": 1, "update_time": 1704418883, "upstream": { "type": "roundrobin", "nodes": { "10.1.23.200:18090": 1 }, "hash_on": "vars", "scheme": "http", "pass_host": "pass" }, "methods": [ "GET" ], "uris": [ "/*" ], "create_time": 1704249167, "plugins": { "prometheus": { "prefer_name": true }, "opentelemetry": { "additional_attributes": [ "deepflow=demo" ], "sampler": { "name": "always_on", "options": { "root": { "name": "always_off" }, "fraction": 0 } } } } }, "key": "/apisix/routes/d60675a2", "modifiedIndex": 1635 } root@k8s-master:~# ``` The operation mentioned above was done around nine o'clock this morning. Now, at one o'clock in the afternoon, when I checked the route again, I found that the plugins content had disappeared again, and I once more verified whether the APISIX-related pods had restarted. ``` root@k8s-master:manifests# curl -s http://10.109.77.186:9180/apisix/admin/routes/d60675a2 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' | jq { "createdIndex": 996, "value": { "desc": "Created by apisix-ingress-controller, DO NOT modify it manually", "id": "d60675a2", "name": "deepflow-otel-spring-demo_deepflow-otel-spring-demo_deepflow-otel-spring-demo", "status": 1, "create_time": 1704249167, "labels": { "managed-by": "apisix-ingress-controller" }, "uris": [ "/*" ], "update_time": 1704430937, "hosts": [ "apisix.deepflow.demo.com" ], "upstream_id": "36119e76", "priority": 0 }, "key": "/apisix/routes/d60675a2", "modifiedIndex": 1655 } root@k8s-master:manifests# root@k8s-master:manifests# root@k8s-master:manifests# kubectl get pods -n apisix -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES apisix-7b4d48bf46-2dqvw 1/1 Running 0 26h 10.244.235.211 k8s-master <none> <none> apisix-dashboard-fd4f97c8c-zdp2k 1/1 Running 0 2d23h 10.244.235.197 k8s-master <none> <none> apisix-etcd-0 1/1 Running 1 (9d ago) 9d 10.244.235.196 k8s-master <none> <none> apisix-ingress-controller-5dbdb8c8d8-zhp7q 1/1 Running 1 (9d ago) 9d 10.244.235.194 k8s-master <none> <none> ``` ### Expected Behavior _No response_ ### Error Logs _No response_ ### Steps to Reproduce I'm not sure how to reproduce the steps, but what I am certain of is that from yesterday to today, the issue has occurred four times. ### Environment - APISIX version (run `apisix version`): - `v3.2 LTS` - Operating system (run `uname -a`): - `Linux k8s-master 5.4.0-164-generic #181-Ubuntu SMP Fri Sep 1 13:41:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux` -- 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]
