etcd CrashLoopBackOff and health check failed about kelemetry HOT 3 CLOSED

is there some problem with your coredns? it seems to say coredns query failed?

from kelemetry.

yes, might be related to coredns, re-deployed again, it seems now it runs well.
However, found below failed error in one pod, not in other two pods log

# kubectl logs kelemetry-etcd-0
...
2023-07-21 01:23:19.283550 W | etcdserver: failed to send out heartbeat on time (exceeded the 100ms timeout for 20.010227ms, to 8359b3cd6960003a)
2023-07-21 01:23:19.283607 W | etcdserver: server is likely overloaded
2023-07-21 01:23:19.283623 W | etcdserver: failed to send out heartbeat on time (exceeded the 100ms timeout for 20.095774ms, to 48518a52c6de43e2)
2023-07-21 01:23:19.283631 W | etcdserver: server is likely overloaded

from kelemetry.

As the error says, this issue seems to be caused by etcdserver getting overloaded. This does not seem to be an issue with Kelemetry, and I cannot reproduce, so I am closing this issue. Feel free to post here if you have further updates.

from kelemetry.