From 03530721b4cf2ecf67f8ef4f29f471cc753abb60 Mon Sep 17 00:00:00 2001 From: Pirate Praveen Date: Wed, 8 Mar 2023 18:50:47 +0530 Subject: [PATCH] Start a sidekiq cluster instead of standalone --- debian/gitlab.gitlab-sidekiq.service | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/debian/gitlab.gitlab-sidekiq.service b/debian/gitlab.gitlab-sidekiq.service index f8b18a3010..6a6e51f06d 100644 --- a/debian/gitlab.gitlab-sidekiq.service +++ b/debian/gitlab.gitlab-sidekiq.service @@ -11,12 +11,11 @@ ReloadPropagatedFrom=gitlab.service Type=simple WorkingDirectory=/usr/share/gitlab EnvironmentFile=/etc/gitlab/gitlab-debian.conf +Environment=SIDEKIQ_QUEUES=* SyslogIdentifier=gitlab-sidekiq ExecStartPre=truncate -s 0 Gemfile.lock ExecStartPre=/usr/bin/bundle install --local --quiet -ExecStart=/usr/bin/bundle exec sidekiq \ - -C /etc/gitlab/sidekiq_queues.yml \ - -e $RAILS_ENV +ExecStart=/usr/bin/bundle exec bin/sidekiq-cluster $SIDEKIQ_QUEUES -e $RAILS_ENV Restart=on-abnormal ## No "Type=notify" support; wait for service to initialise: