otto-de / otto-de/gitactionboard
OOMKilled with 30 repos/120 workflows
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 159
- Forks
- 38
- Avg merge
- 2m
- Merged PRs (30d)
- 10
Description
First, thanks a lot for maintaining the gitactionboard it is a very handy project!
Describe the bug
I run in k8s with ~30 repos and in total ~120 workflows. The Memory limit is set to 3 Gi. I see memory increasing linearly over ~1h after pod start until the pod gets OOMKilled (while the dashboard is open and being refreshed).
Is this a known issue or expected scaling limitation with larger numbers of repositories/workflows? Do you know of any memory leaks or have any recommendations for settings?
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
No source file, test, or entry point is named. Start by reproducing the Kubernetes deployment with about 30 repositories and 120 workflows while the dashboard is refreshed, then monitor memory until the 3 Gi limit is reached. Done means identifying the growth or leak and documenting a verified fix or a confirmed scaling limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kubernetes
- Domain
- devops, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100