Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #8398

Closed
Open
Created Nov 26, 2014 by Administrator@rootOwner

Always busy

Created by: alexchernyy

sidekiq 2.17.0 [25 of 25 busy]

My GitLab version: GitLab 7.4.3, commit https://gitlab.com/gitlab-org/gitlab-ce/commit/353a98757850a37118bc5ff0718d8050f934bf90

Symptoms: Activities not updating in feed (there is no branch in feed if I pushed branch for example); I can not create merge requests because branch is not in source list but pushed on server.

It looks like issue with hooks or sidekiq socket update but gitlab/check command completes without errors and only sidekiq looks strange because it gets 25 of 25 after 'service gitlab reload' . I raised up number of sidekiq workers to 75. 75 of 75 is busy after one working day.

How to debug slow operations? How to determine what blocks background jobs?

Assignee
Assign to
Time tracking