Revolyssup opened a new issue, #10102: URL: https://github.com/apache/apisix/issues/10102
### Current Behavior LRU cache is used to map a group to a limit-count plugin configuration in order to compare newly applied conf with [previous](https://github.com/apache/apisix/blob/704645f6114ce6f2a4fe79857a8049e693f3878c/apisix/plugins/limit-count/init.lua#L185) conf. But when the consumer group is deleted, the cache is not emptied. Due to this when the consumer group is recreated with limit-count plugin with new configuration but previous `group` name, it results in an error as it compares the new config with the previous config of the deleted consumer group.  ### Expected Behavior After the plugin is deleted, the `group` to conf mapping for it should be deleted as well. This will be no problem as there is a 1:1 relationship between `limit-count config<->group` ### Error Logs _No response_ ### Steps to Reproduce 1. Create a limit-count plugin with a group name. 2. Delete that plugin. 3. Try to create limit count plugin with the same group name. ### 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]
