Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
F FLAG
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ras-devel
  • FLAG
  • Issues
  • #3

Closed
Open
Created Apr 23, 2019 by Mitch Burnett@mcbOwner

Gracefully manage hangs

Resolving processing pipeline hangs (#1) is a critical task. Our hashpipe plugin implementing a state machine has an unknown transition resulting in a hang. The idea is to add logic to detect that we are hanging and to notify the user (or log the event) and gracefully catch up and continue processing.

As mentioned in the reported hanging issue (#1) one case is identified in the net thread and signaled with the print statement NET: HANGING HERE!!!. An approach might be to exam that loop where the statement is first printed and then determine the ways we can enter that loop and identify if we can exit and begin processing again.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking