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
ci.jenkins.io
disk almost full
#3492
Comments
steps foreseen :
|
to increase over 512Gib we will have to change to 1024Gib disk and then change of Disk tiers |
We discovered that It's the directory where https://plugins.jenkins.io/jobConfigHistory/ stores the "config changes". The current setup is the default one: we could set up some of the best practises from https://docs.cloudbees.com/docs/cloudbees-ci-kb/latest/best-practices/jobconfighistory-best-practices to decrease the disk usage (move it on another drive?) and improve I/O performances for ci.j (at least removing the |
Ping @MarkEWaite , could you share what you did in #2736 last time it happenned? |
I think that I deleted history. I think that we should remove that plugin from the ci.jenkins.io instance and accept that job configuration history is not worth the disc space penalty |
|
=> cleaning up led to a size of 5.6 Gb |
|
As seen with @smerle33 , the next "culprit" will be the top-level item "Websites" which weight more than 30 Gb !! |
=> the disk is used by the archived ZIP for each build. Let's remove them:
|
This issue is closeable as we went under the 80% usage bar (requirement for good I/O performances). A few improvement (to be treated as separated issues) as discussed with team:
|
Closing the issue as operation is finished! |
Post-cleanup: @smerle33 ran an ncdu analysis, and found a 61 Gb tgz file in |
Final status:
|
this need to be fixed.
Originally posted by @smerle33 in #3491 (comment)
The text was updated successfully, but these errors were encountered: