# K3s.service stops working

**URL:** <https://forums.suse.com/t/k3s-service-stops-working/41897>\
**Category:** k3s, k3OS, and k3d\
**Created:** [November 7, 2023, 10:48pm UTC](https://forums.suse.com/t/k3s-service-stops-working/41897 "2023-11-07T22:48:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elronzo](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/elronzo/32/9971_2.png) [@elronzo](https://forums.suse.com/u/elronzo)\
**Post date:** [November 7, 2023, 10:48pm UTC](https://forums.suse.com/t/k3s-service-stops-working/41897/1 "2023-11-07T22:48:56Z")

</div>

I am observing a strange behaviour in my k3s-Testcluster built of 6 virtual machines (3 masters, 3 workers). Sometimes, when I do some operations with kubectl (e.g. deleting a pod) k3s.service stops working on my master nodes.

I am seeing etcd messages like

`"leader failed to send out heartbeat on time; took too long, leader is overloaded likely from slow disk"`

or

`"apply request took too long","took":"100.464864ms","expected-duration":"100ms"`

Which countermeasures could I possibly take here?

---

<div class="post-metadata">

**Author:** ![malcolmlewis1](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis1/32/10022_2.png) [@malcolmlewis1](https://forums.suse.com/u/malcolmlewis1)\
**Post date:** [November 7, 2023, 11:20pm UTC](https://forums.suse.com/t/k3s-service-stops-working/41897/2 "2023-11-07T23:20:11Z")

</div>

@elronzo Hi and welcome to the Forum 😄  
Sounds like your setup has some disk i/o issues that need to be resolved… Maybe check on the systems in the cluster with top and iostat in the first instance. Are these physical nodes, or vm’s?