Sidekiq concurrency not respected
Summary
I would like to reduce the concurrency of sidekiq. (Or number of threads).
I have set in config/sidekiq.yml
:
---
:concurrency: 2
But that doesn't works. I still have 25 threads. Any idea of where I need to set the concurrency value? (I'm on 8.16.4, manual install).
Steps to reproduce
Modify config/sidekiq.yml
with a custom value. Restart gitlab. Check with ps -eLf | grep sidekiq
. There is still 25 threads.
Expected behavior
Number of sidekiq's threads should be the value setted in config/sidekiq.yml
.
Actual behavior
The value of concurrency is ignored.
Relevant logs and/or screenshots
$ cat config/sidekiq.yml
---
:concurrency: 2
$ ps -eLf | grep sidekiq
gitlab-+ 7595 1 7595 0 31 09:50 ? 00:00:13 sidekiq 4.2.7 gitlab [0 of 25 busy]
gitlab-+ 7595 1 7597 0 31 09:50 ? 00:00:03 sidekiq 4.2.7 gitlab [0 of 25 busy]
gitlab-+ 7595 1 7661 0 31 09:50 ? 00:00:07 sidekiq 4.2.7 gitlab [0 of 25 busy]
gitlab-+ 7595 1 7662 0 31 09:50 ? 00:00:02 sidekiq 4.2.7 gitlab [0 of 25 busy]
[…]
Output of checks
Results of GitLab application Check
Checking GitLab Shell ...
GitLab Shell version >= 4.1.1 ? ... OK (4.1.1)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by gitlab-demo00:gitlab-demo00?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
1/1 ... ok
2/2 ... ok
1/3 ... ok
Running /home/gitlab-demo00/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /home/gitlab-demo00/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... skipped (no tmp uploads folder yet)
Init script exists? ... yes
Init script up-to-date? ... yes
projects have namespace: ...
1/1 ... yes
2/2 ... yes
1/3 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.3)
Your git bin path is "/usr/bin/git"
Git version >= 2.7.3 ? ... yes (2.11.0)
Active users: 2
Checking GitLab ... Finished
Results of GitLab environment info
System information
System: Debian 8.7
Current User: gitlab-demo00
Using RVM: no
Ruby Version: 2.3.3p222
Gem Version: 2.5.2
Bundler Version:1.7.4
Rake Version: 10.5.0
Sidekiq Version:4.2.7
GitLab information
Version: 8.16.4
Revision: 5d1fb2900a
Directory: /home/gitlab-demo00/gitlab
DB Adapter: postgresql
URL: https://demo00.gitlab.[REDACTED]
HTTP Clone URL: https://demo00.gitlab.[REDACTED]/some-group/some-project.git
SSH Clone URL: gitlab-demo00@demo00.gitlab.[REDACTED]:some-group/some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 4.1.1
Repository storage paths:
- default: /home/gitlab-demo00/repositories/
Hooks: /home/gitlab-demo00/gitlab-shell/hooks/
Git: /usr/bin/git