-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
high cpu usage and not working scaphandre #166
Comments
Hi @fcomte, since it works without the For one of the scaphandre containers can you post its cgroup file? The metric has a label with the pid.
The format of the file depends on the cgroup driver being used by the kubelet.
This may be fixed by #146 if you want to try it out you could edit the daemonset to use Hope that helps! |
Thx @rossf7. I have this format :
|
@fcomte Thanks for checking. This format is supported so its something else. Are there any other errors in the logs? If you haven't already can you enable backtraces via the helm chart? scaphandre/helm/scaphandre/values.yaml Line 19 in 8273ced
|
running with backtrace full :
|
Thanks @fcomte I've created #173 to fix the parse int error. There is a problem fetching the pods metadata but with this fix it will retry. Currently each scaphandre instance lists all pods in the cluster but it only needs the pods on the current node. I'm not certain this is the reason pods can't be listed but it would be more efficient to filter for just the current node. @bpetit I'd like to work on this enhancement. I'll let you know how I get on. |
Here is the PR to only list pods for the current node. |
Bug description
I am running scaphandre with the helm package from this repo.
I am unable to get metrics and when I look at the cpu usage of scaphandre, it's very high.
In the logs with some debug trace I have the following exception :
I tried to use directly : docker run on the kubernetes host (without options --containers) and metrics works.
The text was updated successfully, but these errors were encountered: