Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • scalability scalability
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 346
    • Issues 346
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.comGitLab.com
  • GitLab Infrastructure TeamGitLab Infrastructure Team
  • scalabilityscalability
  • Issues
  • #240
Closed (duplicated) (duplicated)
Open
Issue created Mar 24, 2020 by Bob Van Landuyt@reprazent3️⃣Maintainer

Remove support for configuring sidekiq_cluster next to sidekiq from omnibus

For after #239 (closed) we need to remove support for configuring sidekiq_cluster next to sidekiq. Configuring sidekiq cluster will need to be done through sidekiq['*'] in gitlab.rb.

  1. sidekiq_cluster[*] is no longer a thing.
  2. We stop using bundle exec sidekiq altogether.
  3. Everything related to sidekiq is set using sidekiq[*]. sidekiq['enable'] decides if there is a sidekiq service or not - we don't even need sidekiq['cluster'].
  4. The service spawned is sidekiq, but it will run sidekiq-cluster under the hood. It is managed by gitlab-ctl commands to sidekiq
  5. The logs go to /var/log/gitlab/sidekiq.
Edited Apr 24, 2020 by Bob Van Landuyt
Assignee
Assign to
Time tracking