sameersbn / sameersbn/docker-gitlab
one background job in busy state permanently and CPU usage high very frequently with many bundle processes
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Currently it's on 18.6.2 but I think this issue on my setup existed for a long time.
Noticing that there is highly likely always one background job in busy state (see attached screenshot below).
Tried to stop/kill it but it was then kicked again soon.
Also, the CPU is occupied by many bundle processes (see attached screenshot below).
I have also checked around the log files but didn't see an error in interest.
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
Reproduce the behavior with the reported 18.6.2 setup, beginning with the background-job and bundle-process listings shown in the screenshots. Inspect the available log files and process activity; done means identifying why a job remains busy and why CPU usage stays high, then confirming the behavior no longer recurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100