OpenSlides / OpenSlides/openslides-backend
[ReAct] Locking order
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 40
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 19
Description
- to make deadlocks less likely, it might be a good idea to have an order in which collections are locked wherever possible. I.e. if there’s a choice in what to lock next, lock the collection that is first in f.e. the alphabet before the others.
- This won’t exactly be all-encompassing, since the order is also partially determined by the model, the action is supposed to change, but it still will keep some actions out of each others ways.
- A second option would be to find a metric of how often a certain foreign key is used and therefore the model should be requested first. More common ones first.
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
No files, tests, or entry points are named. Start by locating the ReAct code that chooses collection or model locking, then determine whether an ordering or foreign-key usage metric is feasible. Done should include an agreed locking strategy and evidence that it reduces deadlock risk without violating action or model ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100