nic-chen opened a new issue #2396: URL: https://github.com/apache/apisix-dashboard/issues/2396
# Background At present, the connection between the Manager API and etcd still follows the habit of the etcd v2 version, creating a watch connection for each resource, which will generate a large number of connections. # Purpose Reduce the number of connections between Manager API and etcd, to reduce the load on etcd services. # Proposal In the `Generic Store`, each resource still manages its own cache separately, but no longer connects directly to etcd. Added a unified method of fully reading data and watching changes, and the obtained data is uniformly distributed to the Store instances of each resource. After optimization, the workflow of `Generic Store` initialization is as follows: 1. Create a resource prefix mapping table 2. Initialize each resource Store object and register itself in the resource prefix mapping table 3. Read the full amount of data, find the corresponding resource according to the key prefix, and distribute the data to the Store object of each resource 4. Watch the etcd prefix configured in `conf.yaml`, when obtaining the changed data, find the corresponding resource according to the key prefix, and distribute the data to the Store object of the resource. The current connections between Manager API and etcd:  After optimization, the connections between Manager API and etcd:  -- 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]
