-
Notifications
You must be signed in to change notification settings - Fork 88
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 spikes #20
Comments
Would be interesting to know what happens there. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
It was not addressed but it is still an issue IMHO. |
@pascalandy Can you exec into the container when this happens? Or get some |
I can but what are you looking for?
|
Well, if it is the shepherd container which is using the CPU, it would be interesting to see if it is the shepherd script itself or the docker client. I can't really make a picture of this currently. |
I saw this using prometheus and Graphana. Other containers were running normally. So let's close this if you prefer. |
Yes, let's close this for now. Feel free to reopen if you get to the cause. |
I can observe CPU spikes (it's the container that uses the most CPU over 70 services/containers). I'll experiment with CPU limits and report :_p
The text was updated successfully, but these errors were encountered: