Adjust jenkins disk space thresholds
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 542
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
Based on the discussion below we should look at the disk space thresholds that jenkins uses before bringing machines offline. It looks from the message referenced below that the threshold was about 200MB which is far less than the 3-4GB used for a single additional extract. We should revisit that figure to ensure that in a heavy load scenario jenkins can take the machine offline before it causes a problem in the jobs.
@sxa unfortunately this has taken test-mnx-ubuntu2204-x64-1 offline in Jenkins:
It is also causing git checkout failures, e.g. https://ci.nodejs.org/job/node-test-commit-plinux/65613/console
... Resolving deltas: 100% (861498/861498), done. fatal: sha1 file '.git/objects/pack/tmp_idx_BwgFWa' write error: Disk quota exceeded fatal: fetch-pack: invalid index-pack output ...
Originally posted by @richardlau in #6556
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Jenkins disk-space threshold configuration and review the referenced computer test-mnx-ubuntu2204-x64-1 and job node-test-commit-plinux/65613 console output. Done means the threshold is high enough to account for the 3–4GB extract and machines go offline before disk-quota checkout failures occur.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100