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.

Sign up for GitHub

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

Jump to bottom

[Bug]: Jenkins error high CPU utilization. #179

Closed
prudhvigodithi opened this issue Aug 4, 2022 · 1 comment
Closed

[Bug]: Jenkins error high CPU utilization. #179

prudhvigodithi opened this issue Aug 4, 2022 · 1 comment
Assignees
@prudhvigodithi
Labels
bug Something isn't working

Comments

@prudhvigodithi
Copy link
Member

prudhvigodithi commented Aug 4, 2022 •
edited
Loading

Describe the bug

Jenkins Runs fine, UI is up and builds work fine as well, but backend docker stats shows the CPU utilization percentage is too high and triggers the alerts.
Existing instance type is using c5.4xlarge which has 30GB and 16CPU, lot of host resources are being unused.

To reproduce

N/A

Expected behavior

No response

Screenshots

If applicable, add screenshots to help explain your problem.

Host / Environment

No response

Additional context

No response

Relevant log output

No response
@prudhvigodithi prudhvigodithi added bug Something isn't working untriaged Issues that have not yet been triaged labels Aug 4, 2022
@prudhvigodithi prudhvigodithi changed the title [Bug]: Jenkins error hight CPU utilization. [Bug]: Jenkins error high CPU utilization. Aug 4, 2022
@prudhvigodithi prudhvigodithi removed the untriaged Issues that have not yet been triaged label Aug 4, 2022
This was referenced Aug 4, 2022
Merged
Merged
@prudhvigodithi prudhvigodithi self-assigned this Aug 4, 2022
@rishabh6788
Copy link
Collaborator

The CPU alarm has been corrected. #182

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@prudhvigodithi prudhvigodithi

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rishabh6788 @prudhvigodithi