chaoss / chaoss/grimoirelab-sortinghat
Scheduled jobs don't run after crash
Open
- Dominant language
- Python
- Stars
- 58
- Forks
- 89
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 2
Description
After a demanding query to SortingHat's API, SortingHat eats up the CPU rendering the machine unreachable via SSH.
After a reboot, the scheduled jobs are shown as actively scheduled by SortingHat's settings page, but the scheduled launch time goes by and the jobs don't run. We see weekly scheduled jobs with their last runs dating months ago.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by tracing the scheduled-job lifecycle across a crash and reboot, comparing the settings page's active state with the scheduler's execution state. Done means scheduled jobs launch at their configured times after recovery and their last-run timestamps update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100