Rolling back uncommitted entries in FasterLog
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.6k
- Forks
- 595
- PR merge metrics
- No merged PRs in 30d
Description
I'm currently evaluating Faster for use as a backend for a distributed system synchronized using raft. Is it currently possible to rollback uncommitted entries from FasterLog ?
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
Start by reviewing FasterLog's handling of committed and uncommitted entries, then compare that behavior with the rollback requirement described for Raft synchronization. No files, tests, or entry points are named in the issue; completion would require establishing whether rollback is supported and defining the needed behavior if it is not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100