TheHive-Project / TheHive-Project/Cortex
Aborted jobs are still showing up as InProgress after Cortex restart
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.6k
- Forks
- 264
- PR merge metrics
- No merged PRs in 30d
Description
Request Type
Bug
Work Environment
| Question | Answer |
|---|---|
| OS version (server) | Ubuntu 18.04 LTS |
| OS version (client) | not relevant |
| Cortex version / git hash | 3.1.1-1 |
| Package Type | Debian package |
| Browser type & version | not relevant |
Problem Description
Running jobs are not marked as failed or something similar on unexpected abortion (stop/restart) of Cortex.
Steps to Reproduce
- Run many analyzers
- Suddenly stop Cortex while the analyzers are still running
- Start Cortex again
- See previously "running" analyzers still showing up as "InProgress" while they are actually not
Possible Solutions
There are two options:
- Re-run the analyzer job (probably not a good idea for responders) on Cortex startup
- Mark the job as failed or aborted
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing Cortex startup handling and the persisted state of analyzer jobs after an unexpected stop. Reproduce the restart scenario described in the issue and verify that jobs interrupted during shutdown are marked failed or aborted rather than remaining InProgress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100