-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tallow eating 100% of 1 CPU thread #15
Comments
What happens when you kill tallow? |
Oh, that was months ago ;-), and I don't think I've (knowingly) seen it since. |
I myself encountered the issue a few months back, which is why I'm keeping this open. I have not yet determined whether this bug is gone now (e.g. due to some of the recent large changes) or not |
Hi. I came across the exact same issue as @grahamwhaley did. The problem was solved by killing and restarting tallow. I have noticed it will happen when you are in a SSH-session for too long (over 30 hours (Don't ask me why I was in a session for so long)). This issue is still a problem on the newest Clear Linux OS, and I have seen the error on my system multiple times now. it would be really nice if you could take a look at it ;-) My machine:
|
I second that in 2022 on Clear Linux, so the symptom is tallow restarts who knows why, and gets 100% on its little thread. Thank God CPUs have more cores nowadays! :) |
Same issue here, noticed performance was a bit off on a huge batch job in Ruby that I run frequently, and turns out |
I just observed this as well
|
I noticed in top that
tallow
was consuming 100% of a cpu thread.A
gdb
attach shows its stack as:A continue/stop then showed it as:
The tallow journal looks like:
The only 'interesting' thing on this machine is that it is running a single node k8s cluster.
The machine is:
The text was updated successfully, but these errors were encountered: