Hi Community. Currently, server-info plugin adds a revision every time the status is updated, and some users set a relatively short reporting time, which may result in millions or even tens of millions of data in etcd after a long run, resulting in a slow connection and high cpu usage. So I give a proposal to refractory the server-info plugin.
Here is a new implement: 1. get the server-info data, if it does not exist, initialize the server-info information 2. bind the lease to the key "server-info" 3. call keepalive to refresh the TTL to ensure the node is alive Flowchart: [image: image.png] What about your opinions?