Skip to content
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

cpu saturated after containerd.service restart #2748

Closed
hanlins opened this issue Dec 3, 2020 · 0 comments · Fixed by #2749
Closed

cpu saturated after containerd.service restart #2748

hanlins opened this issue Dec 3, 2020 · 0 comments · Fixed by #2749

Comments

@hanlins
Copy link
Contributor

hanlins commented Dec 3, 2020

This issue was found during the investigation of kubernetes/kubernetes#95727.

Description:
After cadvisor manager starts, if containerd got restarted, it will get into a loop and flooding timeout.

Reproduce:
To reproduce the issue, you just need to create a cadvisor manager and start it, then restart containerd. For simplicity, created a repo, and you can reproduce the issue on a environment with containerd running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant