Skip to content

Use Sidekiq Cluster by default for GDK

Oswaldo Ferreira requested to merge osw-use-sidekiq-cluster-by-default into master

What does this Merge Request do?

We're moving towards making Sidekiq Cluster the new default for every installation, and that includes GDK (see gitlab-com/gl-infra&181 (closed)).

Currently Sidekiq Cluster is used at GitLab.com and big EE customers' scale meaning that putting it in front of developers can prevent issues from flowing to other environments (specially if we run multiple processes on GDK in the future).

With this change we're making Sidekiq Cluster spin a single Sidekiq process by default through the bin/background_jobs script. Mapping the same behavior it used to have while running sidekiq directly.

Removing the SIDEKIQ_WORKERS env var will make it fall back to the old bundle exec sidekiq behavior (if any issue arise).

This MR is specially related and depends on gitlab!27042 (merged).

gitlab-com/gl-infra/scalability#197 (closed)

Merge Request checklist

  • Tests added for new functionality. If not, please raise Issue to follow-up.
  • This change is backward compatible. If not, please include steps to communicate to our users.
  • Documentation added/updated, if needed.
  • gdk doctor test added, if needed.
Edited by Oswaldo Ferreira

Merge request reports