Replies: 1 comment 1 reply
-
Your disk performance is not sufficient to meet the needs of the applications you are deploying. I'm not sure how this is an rke2 issue? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Environmental Info:
RKE2 Version: 1.27.15
Node(s) CPU architecture, OS, and Version: LinuxRHEL 4.18.0-553.22.1.el8_10.x86_64 #1 SMP Wed Sep 11 18:02:00 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration: 3 Controllers and 5 workers
Describe the bug: During last month we see several everyday Disk I/O saturation inside of workers during some jobs backup, jobs from longhorn or runners from gitlab.
this ever happend in partitions dm- / sda
When this saturation is higher and higher, many of my pods dead and if is the case that pod got a Volume, the volume regards attached from that pod and that pod never restart. I need to kill but I need to restart the service from rke2-agent from that worker.
it is so frustating this ever happend everyday and I dont know what to do
Steps To Reproduce:
Expected behavior: Low disk I/O saturation and NO worker stop working
Actual behavior: Very high saturation and workers stop working.
Additional context / logs:
Beta Was this translation helpful? Give feedback.
All reactions