IDs of task can duplicated when mvсс is on
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 244
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
To minimize the possibility of conflicts, MVCC uses what is called best-effort visibility: for write transactions it chooses read-committed, for read transactions it chooses read-confirmed.
by default task_id:max read confirmed , this is the key reason why duplicates occur in the case of an race condition
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
Start by reading queue/abstract/driver/fifo.lua at lines 70–73 and review how task_id:max is read under MVCC. Reproduce the race condition described in the issue, then determine and verify a change that prevents duplicate task IDs when concurrent operations use read-confirmed visibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100