Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab Development Kit
GitLab Development Kit
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 308
    • Issues 308
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 49
    • Merge Requests 49
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab Development KitGitLab Development Kit
  • Issues
  • #856

Closed
Open
Opened Apr 03, 2020 by Ash McKenzie@ashmckenzieMaintainer

Include 'stale process' detection as part of gdk doctor

Overview

At times, some GDK services can become 'stale' and are not able to be stopped via gdk stop/restart. A recent example is rails-background-jobs didn't stop properly but instead returned a state of timeout and needed intervention outside of the gdk command line tool (e.g. kill <pid>).

Related

  • gitlab-com/gl-infra/scalability#270 (closed)
  • #864 (closed)

Proposal

As a first iteration, update gdk doctor to look at rails-background-jobs for now to see if it's 'stale' and make recommendation(s) to address.

Edited Apr 29, 2020 by Ash McKenzie
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-development-kit#856