Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
High CPU usage after pod deletion with layer2 #246
Is this a bug report or a feature request?:
When an interface (pod) was deleted the speaker cpu usage went above >100% until it was restarted.
What you expected to happen:
Things remain "normal".
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
The NDP responder wasn't created for the pod interface, which may or may not have anything to do with this:
Okay, takes a couple of attempts to reproduce, but I can trigger this, 170% CPU utilization from speaker. The logs suggest it went through the normal/correct deletion sequence for the torn-down network interface, so... Hmm. Needs more logs in the responder goroutine.