-
Notifications
You must be signed in to change notification settings - Fork 229
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
dbus hang when call godbus client in kubelet #221
Comments
The lock mentioned in this stack trace doesn't seem to belong to godbus: it looks to be from a vendored copy of runc's libcontainer. What do you believe godbus is doing wrong? Searching for some keywords from the trace turned up kubernetes/kubernetes#92855, which is marked fixed. So does the problem go away if you upgrade kubernetes? |
Thanks for response @jhenstridge . 92855 is not the same issue. We find the client is hang and not response when call |
I suspect you're probably hitting the bus daemon's On a quick code search, it isn't clear to me that the daemon will synthesise error messages when this happens (it is a DoS protection, after all), which could lead to your code waiting forever. One way to test this would be to set If this is the issue, I guess that leaves open the question of whether godbus should rate limit method calls on a connection. If other D-Bus client bindings to so, then I can see an argument for doing that. If not, then perhaps kubelet should do something to limit its parallelism here? |
On further inspection, it looks like you should get a |
Can you determine which version of godbus is actually used there? Also k8s 1.15 is EOL as far as I know |
We use 1.15 kubelet and find the dbus will hang when lots of containers create. Other containers will wait the lock release.
The text was updated successfully, but these errors were encountered: