TheHive-Project / TheHive-Project/Cortex
Cortex website and API not responding to requests
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
Cortex website and API not responding to requests.
Steps to Reproduce
A few minutes after (re)starting Cortex and a couple of jobs have been run, it is getting stuck, unresponsive or extremely slow.
Complementary information
Workaround relaxing the situation a bit, but not permanently
The following akka configuration helped a little bit, but Cortex will still end of unresponsive after a day or so:
# Debugging and workaround for performance issues
akka {
log-config-on-start = on
actor {
default-dispatcher {
fork-join-executor {
parallelism-max = 16
}
thread-pool-executor {
fixed-pool-size = 16
}
throughput = 1
}
default-blocking-io-dispatcher {
fork-join-executor {
parallelism-max = 32
}
thread-pool-executor {
fixed-pool-size = 32
}
throughput = 1
}
}
}
It seems like definitely having more blocking I/O dispatchers (whichever executor is used) than normal dispatchers is helping, but not solving with the issue.
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 with thread-dump.txt and the reported Cortex 3.1.1-1 environment, then reproduce the slowdown after restarting Cortex and running a few jobs. Compare behavior with the supplied Akka dispatcher configuration; done means the website and API remain responsive rather than becoming stuck or extremely slow after extended operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100