Closed harridu closed 1 week ago
PS: K3s has the same problem.
@harridu I had exactly the same issue https://github.com/rancher/rke2/issues/6249
Do you store etcd snapshots on s3 storage ?
Please upgrade to v1.28.11+rke2r1
@brandond BTW I still don't see option to upgrade rke2 to 2.18.11 from Rancher. Do you have any info when it will be available? Because I still during few weeks have to go and manually clear my bucket
@serhiynovos , yes, I am using a local minio to store a copy of the snapshots.
Update: S3 snapshots were on, but they are disabled right now. Only local storage.
@harridu Please check your bucket. There should be a lot of snapshots. You can clean them manually and see if it will resolve the issue.
deleted. How comes the S3 storage is still in use, even though it is disabled in the GUI?
After removing all backups in S3 rke2 memory usage stays low, as it seems.
I still have no idea why it backups to S3 at all. If 1.28.11 provides some fixes, then please make it available in Rancher 2.8.5.
I still have no idea why it backups to S3 at all.
I'm not sure what you mean. Why does it back up to S3 when you configure s3 for backups?
I still have no idea why it backups to S3 at all.
I'm not sure what you mean. Why does it back up to S3 when you configure s3 for backups?
@brandond i think @harridu means that on rancher ui he disabled s3 backups but rke2 still uploads them on s3 storage.
Btw finally got 1.28.11 version on Rancher. Issue with s3 is resolved
Please upgrade to v1.28.11+rke2r1
For us that are on v2.8.4
or v2.8.5
of Rancher without Prime don't have the option to pick 1.28.11+rke2r1
, it's not part of the supported rke2 releases at least. Technically we could of course deploy 1.28.11
but we have had problems before when deploying a later version than the one specified for the specific Rancher release.
Any suggestions or input on this?
Upgrade to 2.9.0, or deal with running newer RKE2 releases that are not technically supported by the patch release of Rancher that you're on.
Upgrade to 2.9.0, or deal with running newer RKE2 releases that are not technically supported by the patch release of Rancher that you're on.
Thanks!
As a side note: We just noticed that when we in Rancher (the UI) check RKE2 versions we can select version 1.28.11
but in the release notes for the version we're on 2.8.4
that version is not mentioned: https://github.com/rancher/rancher/releases/tag/v2.8.4. Is the list of versions we can upgrade to dynamically updated perhaps?
It is, yes.
Closing as resolved in releases that have a fix for the s3 snapshot prune issue.
Environmental Info: RKE2 Version:
Node(s) CPU architecture, OS, and Version: Debian12 running inside kvm, 4 cores, 32 GByte memory, no swap
Cluster Configuration: 3 controller nodes, 32 GByte RAM and 4 cores each, kvm 6 "real" worker nodes, 512 GByte RAM and 64 cores each All Debian 12, RKE2 1.28.10, managed in Rancher 2.8.5
Describe the bug: On the control plane nodes rke2 uses up quite a big chunk of memory. On the first control node I get
That is 20 GByte rss. On the other control plane nodes it is "just" 3 GByte. Still way too much for 3 days uptime. Memory usage increases over time, till the first control plane nodes runs into OOM.
The worker nodes seem fine.
Steps To Reproduce: Setup a cluster using Rancher 2.8.5 and RKE2 1.28.10 and see it grow. If I use RKE2 on the command line to setup a cluster there is no such problem.