Commit thread in separate fiber
Open
Nobody has claimed this yet.
Replication
- Dominant language
- C++
- Stars
- 29
- Forks
- 30
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 6
Description
commit thread doing a lot , make it run under another fiber in Home object,where we write to index and respond to the client for both follower and leader. - Improvements/Verification.
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 tracing the Home object’s commit thread and the paths that write to the index and respond to clients for followers and leaders. Determine how that work is coordinated before assessing whether it can run in a separate fiber. Done means the commit work is separated without breaking index updates or either client-response path, with verification covering both roles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100