https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
h
k3s version:
Copy code
k3s version v1.30.3+k3s1 (f6466040)
go version go1.22.5
os version:
Copy code
Ubuntu 22.04.5 LTS
Cluster:
Copy code
CTL: 2 vCPU, 2Gb RAM
Worker 1: 8 vCPU 16Gb RAM
Worker 2: 8 vCPU, 16 Gb RAM
Datastore: 4 vCPU, 8 Gb RAM
Datastore type: MySQL 8
Run command for debug and gather logs:
Copy code
/usr/local/bin/k3s server '--tls-san' '192.168.0.200' '--datastore-endpoint' '<mysql://user:password@tcp>(192.168.0.199:3306)/k3s'         '--token' 'token'--log' '/var/log/rancher/k3s.log' -v 0
Database size after 7 days usage: 1.8 Gb.
After first try to address the problem there was some actions performed:
Copy code
SELECT * FROM ( SELECT count(1) num, NAME FROM kine GROUP BY `name` ) ab ORDER BY num DESC;
Result is on screenshot 1.
Copy code
SELECT name, COUNT(*) FROM kine GROUP BY name HAVING COUNT(*) > 5000;
Result is on screenshot 2.
Copy code
SELECT COUNT(*) AS total_rows
FROM kine 
WHERE id IN (
    SELECT id FROM (
        SELECT id, name 
        FROM kine 
        WHERE id NOT IN (
            SELECT MAX(id) 
            FROM kine 
            GROUP BY name
        )
    ) AS temp
);
Returned 747579.
Copy code
DELETE FROM kine 
WHERE id IN (
    SELECT id FROM (
        SELECT id, name 
        FROM kine 
        WHERE id NOT IN (
            SELECT MAX(id) 
            FROM kine 
            GROUP BY name
        )
    ) AS temp
);
After deleting that records cluster become responsive and fully operational from the first look.
After 7 days of cluster work I have the next results: 602763 rows
Open in Slack
PreviousNext
Powered by