GPL-750 BUG - too high number of threads when generating the positive samples report
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
From mail:
Our monitoring system is again warning us that there are more than 300 concurrent connections to MLWH, and as before, this is due to the sudden appearance of a large number (241) connections They appeared at around 11:30, and they have been idle for the past 50 minutes.
RT Ticket Number
If applicable
To Reproduce
Steps to reproduce the behaviour:
- Go to mlwh
- Run:
show status; - See number for 'threads_connected'.
Expected behaviour
The number of max threads is 500 and is shared with everybody using the MLWH database. We should not create 200 threads just for creating a report.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- Windows or Mac?
- Browser Chrome, Firefox, Safari or other?
- Browser version (use 'About' to look up)?
Additional context
Add any other context about the problem here.
Contributor guide
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 locating the positive samples report generation entry point and trace how it creates database connections or threads. Reproduce the issue with show status in MLWH, then confirm the report no longer creates hundreds of idle connections while still completing successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100