database lock issue
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.6k
- Forks
- 1.2k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 16
Description
Hi,
in some modules when there are a lots of events submitting to db, i got a lot of failure error with database lock, we need to re-architect the whole thing, it use a lots of IO, unnecessary memory, CPU, etc.
Bests. Ali.
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
No file, module, database engine, or test is named. Start by identifying the modules that submit many events and reproducing the database-lock failures; done would require an agreed redesign that addresses the reported I/O, memory, CPU, and locking problems, plus tests demonstrating reliable event submission.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100