ETCD getting "apply request took too long" log frequently #9207
Replies: 3 comments 10 replies
-
Can you provide CPU utilization and disk iops stats from this node over the time period in question? I'm not aware of anything that will cause this other than not having sufficient resources for etcd. |
Beta Was this translation helpful? Give feedback.
-
After making cpu and memory high , the etcd logs has been reduced in last 4 hours i can only few logs
i can see the pattern after this reindex logs only few logs comings !!! this also related to disk i/o or resource utilization ? |
Beta Was this translation helpful? Give feedback.
-
same case for me on k8s v1.28.4, |
Beta Was this translation helpful? Give feedback.
-
Environmental Info:
K3s Version: v1.28.4+k3s2
Node(s) CPU architecture, OS, and Version: 8vCPU with 32GB memory
Cluster Configuration: [3node master+ worker cluster]
Describe the bug:
Hi all,
I am using k3s 1.28 version with embedded etcd for the HA cluster,
i can see the too long warning logs, often , asper k3s and etcd recommendation i made /var/lib/etcd as a sperated SSD[ azure premium disk ] with 7.2k I/O [too high] but still this is coming ...
the problem is after some days like 90+ the etcd cluster became unstable and sometimes corrupted too, i suspect this slow disk was the issue, but keeping I/O and throughput high also nothing making any difference,
can anyone just explain, what may be the issue?
If any particular details are needed, let me know will try to share ASAP
Beta Was this translation helpful? Give feedback.
All reactions