sameersbn / sameersbn/docker-gitlab
Redis::TimeoutError
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I have a kubernetes setup running you docker-gitlab, docker-redis, ... containers. Sometimes i get Redis::TimeoutError when i commit something to gitlab. I tried a lot to fix this and the issue happens less often.
The best improvement till now was to add a slave node and only persist redis on slave(running master with save "") but i still get this error.
I tried to increase timeouts in gitlab-shell but this is not easy since gitlab-shell config gets generated while container start.
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 reproducing the Redis::TimeoutError during a GitLab commit in the described docker-gitlab, docker-redis, and Kubernetes setup. Inspect the generated gitlab-shell configuration and the reported Redis persistence and timeout settings; done means the commit path no longer intermittently raises Redis::TimeoutError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab, kubernetes, redis
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100