Skip to content
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

bug: apisix 3.x lost config cache values after etcd compacted #8682

Closed
zlhgo opened this issue Jan 14, 2023 · 2 comments · Fixed by #8736
Closed

bug: apisix 3.x lost config cache values after etcd compacted #8682

zlhgo opened this issue Jan 14, 2023 · 2 comments · Fixed by #8736
Assignees
Labels
bug Something isn't working

Comments

@zlhgo
Copy link
Contributor

zlhgo commented Jan 14, 2023

Current Behavior

local dir_res, headers = res.body.list or {}, res.headers

Perhaps should be

local dir_res, headers = res.body.node or {}, res.headers

#8675 has the same problem.

Expected Behavior

No response

Error Logs

No response

Steps to Reproduce

etcdctl compact `etcdctl get -w json /apisix/upstreams/ | jq .header.revision`

Perhaps this command should be run multiple times.
2. do not update related keys, for example global_rules.
3. wait a moment, the global plugins not working.

Environment

  • APISIX version (run apisix version): 3.1.0
  • Operating system (run uname -a):
  • OpenResty / Nginx version (run openresty -V or nginx -V):
  • etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
  • APISIX Dashboard version, if relevant:
  • Plugin runner version, for issues related to plugin runners:
  • LuaRocks version, for installation issues (run luarocks --version):
@zlhgo zlhgo changed the title bug: apisix 3.x lost config cache values when etcd compacted bug: apisix 3.x lost config cache values after etcd compacted Jan 14, 2023
@zlhgo
Copy link
Contributor Author

zlhgo commented Jan 28, 2023

@tokers 为啥就没人理我呢。

@spacewander spacewander added the bug Something isn't working label Jan 29, 2023
@spacewander spacewander self-assigned this Jan 29, 2023
@spacewander
Copy link
Member

There are some paths that reloaded data may be in res.body.node
Try to fix it via #8736

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants