sameersbn / sameersbn/docker-gitlab
Sidekiq MemoryKiller
Open
Nobody has claimed this yet.
wontfix
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I've been experiencing Sidekiq memory issues since upgrading from Gitlab 9.2.2 to 10.3.5. After some exploration I found that this can be mitigated using environment variables .
I couldnt find anything obvious, is this being configured in this configuration?
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 with the linked GitLab Sidekiq MemoryKiller documentation, then inspect this image's configuration for support for the referenced environment variables. Confirm whether the variables are already passed through or need to be exposed; done means the configuration behavior is documented or supported and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100