BallotBox中是否可以维护每个Peer的matchIndex而不是给每个Log维护一个Ballot以提高commit性能?
Open
- Dominant language
- C++
- Stars
- 4.2k
- Forks
- 923
- PR merge metrics
- No merged PRs in 30d
Description
在BallotBox中只维护每个Peer的matchIndex(每个peer已经commit的Index)。在CommitAt中推高matchIndex,并根据matchIndex判断Majority的commitIndex最小值。
这样是否会比给每个Log维护一个Ballot有显著的Commit性能提升?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the BallotBox CommitAt path and its handling of per-log Ballot values. Compare that behavior with maintaining each peer's matchIndex and deriving the majority commitIndex from the minimum applicable value. Done means a decided design supported by commit-performance measurements and confirmation that commit behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100