Large cohort creation jobs
- Dominant language
- Python
- Stars
- 30
- Forks
- 3
- Avg merge
- 9h 22m
- Merged PRs (30d)
- 40
Description
Someone took down the server by kicking off a 600 sample (7 VCF) cohort job 3 times
* Put a message up saying that if they want to analyse lots of samples (and maybe dividing into lots of sub groups) they are better off merging them into 1 VCF and re-uploading
* If they change the cohort and then re-kick things off, kill the previous database jobs
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by tracing cohort creation and the database job orchestration entry points; then identify where a warning can be shown and where prior jobs can be cancelled when the cohort changes. Done means large cohorts receive the merge-and-reupload guidance and restarting a changed cohort does not leave earlier database jobs running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, databases, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100