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

kubelet/dockerd consume a lot of CPU on Windows node #1482

Closed
zhiweiv opened this issue Mar 10, 2020 · 3 comments
Closed

kubelet/dockerd consume a lot of CPU on Windows node #1482

zhiweiv opened this issue Mar 10, 2020 · 3 comments
Assignees
Labels

Comments

@zhiweiv
Copy link

zhiweiv commented Mar 10, 2020

What happened:
kubelet/dockerd consume a lot of CPU on Windows node, I guess the System interrupts cpu usage is also caused by them.
cpu

I was able to get pprof cpu profile from kubelet.

aks.pb.gz

aks

What you expected to happen:
cpu usage for kubelet/dockerd are normal.

How to reproduce it (as minimally and precisely as possible):
Not sure, only one of our Windows nodes encounters this issue.

Environment:

  • Kubernetes version (use kubectl version): 1.14.8
  • Size of cluster (how many worker nodes are in the cluster?): 2 Linux nodes, 7 Windows nodes
  • General description of workloads in the cluster: .net web/worker
@mikkelhegn mikkelhegn self-assigned this Mar 12, 2020
@jluk
Copy link
Contributor

jluk commented Jun 18, 2020

Closing in favor of support request if still occurring.

@jluk jluk closed this as completed Jun 18, 2020
@mikkelhegn
Copy link
Contributor

@immuzz Can you confirm you're looking into this?

@immuzz
Copy link

immuzz commented Jun 22, 2020

@mikkelhegn Yes we are looking into this issue.

@jluk jluk added the windows label Jun 22, 2020
@mikkelhegn mikkelhegn removed their assignment Jun 23, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jul 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants