-
Notifications
You must be signed in to change notification settings - Fork 550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
data not found by key #2631
Comments
Yes, I have encountered the same problem. Is there a solution? |
I met the same problem |
Since Dashboard places a cache layer in front of etcd in order to reduce requests to and from etcd, it queries etcd and prints this log when there is no corresponding data in the cache layer. This log does not indicate that your system is down and can be ignored. |
@Baoyuantop Is anything that I missed? |
Issue description
In dashboard error.log I see messages like:
2022-09-26T11:22:10.187Z WARN store/store.go:154 data not found by key: 424533355921408701
2022-09-26T11:22:10.187Z WARN store/store.go:154 data not found by key: 424610085914804925
They appear every time when I open Route section in UI.
Key is routes ID.
Message appears on every created route.
All routes work fine.
If I open clean route then message appears anyway.
I started clean APISIX + dashboard instances using docker compose file provided here https://github.com/apache/apisix-docker/tree/master/compose, created clean route and get the same error message.
Expected behavior
"data not found by key" message must not appear on routes that passed validation
How to Reproduce
2022-09-29T07:16:49.252Z WARN store/store.go:154 data not found by key: 427661642814194368
Screenshots
No response
Environment
apisix version
): 2.15.0uname -a
): Linux LAPTOP-189UUVIH 5.10.102.1-microsoft-standard-WSL2 Init Dashboard & add some features #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linuxnginx -V
oropenresty -V
):etcd --version
): {"etcdserver":"3.4.9","etcdcluster":"3.4.0"}Additional context
No response
The text was updated successfully, but these errors were encountered: