Broken SQL Connection pooling about k3s

[brandond]

Kine does use the default golang sql client connection pool support. There is nothing here that is K3s or Kine specific.

Connection pooling does not help you if your database is slow. If a client makes a request from the apiserver that requires a query to the datastore, and there are no pooled connections available (because all the current connections are tied up waiting for an existing query to complete), it will open a new connection. You now have even more queries running, and the database just gets even slower.

I would probably try to figure out why your database is running so slow. Is compaction failing? You should see this in your logs. If it is, you could try manually compacting, or just letting a single K3s server run for a while and see if it is able to compact successfully without additional client load.