Deadlock possible in query evaluation
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 114
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
The easiest way to demonstrate this is to set HalyardTupleExprEvaluation.MAX_QUEUE_SIZE = 1 then try to evaluate "ASK {}". HalyardTupleExprEvaluation.evaluateTupleExpr(root.pipe, expr, bindings) needs to be called on a background thread.
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
Reproduce the issue by setting HalyardTupleExprEvaluation.MAX_QUEUE_SIZE to 1 and evaluating "ASK {}" with HalyardTupleExprEvaluation.evaluateTupleExpr(root.pipe, expr, bindings) on a background thread. Trace the queue and evaluation flow to identify the deadlock, then verify that the same evaluation completes without blocking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100