dramenk opened a new issue, #13067: URL: https://github.com/apache/apisix/issues/13067
### Current Behavior I have been experiencing resource consumption issues due to etcd compaction errors, which led me to review the solution proposed in PR #12514. It appears that APISIX fetches the latest global revision `A` by reading `/phantomkey` (a non-existent key?) before initiating a watch. If the subsequent watch times out without receiving any events, the next iteration uses the previously fetched revision `A` as the start_revision. However, I have a question: If a "silent" error occurs during a watch (with `start_revision:B`), such as a silent network interruption occurring just before etcd sync the historical events, the watch will fail to get those events. If we then update the start_revision for the next watch to `A+1`, wouldn't the historical events between `B` and `A` be permanently lost? Or am I misunderstanding the current implementation? ### Expected Behavior _No response_ ### Error Logs _No response_ ### Steps to Reproduce null ### Environment - APISIX version (run `apisix version`): - 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`): -- 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]
