Nobilta opened a new issue, #7862: URL: https://github.com/apache/apisix/issues/7862
### Description i know that apisix's watch is based on http/1.1,so if i have many route or upstream,apisix will make lots of post request to etcd(such as this paper:https://apisix.apache.org/zh/blog/2021/08/10/apisix-nginx/#%E5%9F%BA%E4%BA%8E-etcd-watch-%E6%9C%BA%E5%88%B6%E7%9A%84%E9%85%8D%E7%BD%AE%E5%90%8C%E6%AD%A5%E6%96%B9%E6%A1%88) so can i use etcd's gRPC proxy(https://etcd.io/docs/v3.5/op-guide/grpc_proxy/) to coalesce watch and improve my performance?if it can be use,why i have some errors in logs,and how can i to fix it ?(i make sure etcd is work,i can use client to control etcd cluster) `lua ./apisix/cli/apisix.lua start Sep 01 19:38:10 apisix[15069]: lua: /usr/local/apisix/apisix/cli/etcd.lua:215: attempt to index local 'body' (a number value) Sep 01 19:38:10 apisix[15069]: stack traceback: Sep 01 19:38:10 apisix[15069]: /usr/local/apisix/apisix/cli/etcd.lua:215: in function 'init' Sep 01 19:38:10 apisix[15069]: /usr/local/apisix/apisix/cli/ops.lua:689: in function 'init_etcd' Sep 01 19:38:10 apisix[15069]: /usr/local/apisix/apisix/cli/ops.lua:752: in function '?' Sep 01 19:38:10 apisix[15069]: /usr/local/apisix/apisix/cli/ops.lua:840: in function 'execute' Sep 01 19:38:10 apisix[15069]: ./apisix/cli/apisix.lua:34: in main chunk Sep 01 19:38:10 apisix[15069]: [C]: ? Sep 01 19:38:10 systemd[1]: apisix.service: control process exited, code=exited status=1 Sep 01 19:38:10 systemd[1]: Failed to start apisix.` ### Environment - APISIX version (run `apisix version`):v2.15 - Operating system (run `uname -a`):centos - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): - etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`):v3.5 - 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]
