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
    • Menu
    Projects Groups Snippets
  • Get a free trial
  • Sign up
  • Login
  • Sign in / Register
  • scalability scalability
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 244
    • Issues 244
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 is launching on May 22! This version brings many exciting improvements, but also removes deprecated features and introduces breaking changes that may impact your workflow. To see what is being deprecated and removed, please visit Breaking changes in 15.0 and Deprecations.

  • GitLab.com
  • GitLab Infrastructure Team
  • scalabilityscalability
  • Issues
  • #240
Closed (duplicated) (duplicated)
Open
Created Mar 24, 2020 by Bob Van Landuyt@reprazentMaintainer

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