-
Notifications
You must be signed in to change notification settings - Fork 23
raft: consensus protocol design doc #100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
SUMUKHA-PK
wants to merge
32
commits into
master
Choose a base branch
from
Consensus-protocol-Design-Doc
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 2 commits
Commits
Show all changes
32 commits
Select commit
Hold shift + click to select a range
5a7a27b
Create Consensus-Protocol.md
SUMUKHA-PK df185c3
Update Consensus-Protocol.md
SUMUKHA-PK 9657559
Merge branch 'master' into Consensus-protocol-Design-Doc
tpdenk 099498a
Update doc/internal/parser/scanner/Consensus-Protocol.md
SUMUKHA-PK 43e600e
Update Consensus-Protocol.md
SUMUKHA-PK bd90b1f
Update Consensus-Protocol.md
SUMUKHA-PK 7d26490
Update Consensus-Protocol.md
SUMUKHA-PK 5923f4f
Update Consensus-Protocol.md
SUMUKHA-PK 02239c8
Update Consensus-Protocol.md
SUMUKHA-PK 2b900c0
Update Consensus-Protocol.md
SUMUKHA-PK 8527df5
Merge branch 'master' of https://github.com/tomarrell/lbadd into Cons…
SUMUKHA-PK b18332a
Moved doc to appropriate folder
SUMUKHA-PK b11486e
Update Consensus-Protocol.md
SUMUKHA-PK 4e559a5
Merge branch 'master' into Consensus-protocol-Design-Doc
SUMUKHA-PK 7eef110
Update Consensus-Protocol.md
SUMUKHA-PK 9b209f1
Merge branch 'master' into Consensus-protocol-Design-Doc
SUMUKHA-PK 17a8e1a
Merge branch 'master' into Consensus-protocol-Design-Doc
SUMUKHA-PK 1cb7555
Merge branch 'master' into Consensus-protocol-Design-Doc
SUMUKHA-PK 1209205
Update doc/internal/consensus/Consensus-Protocol.md
SUMUKHA-PK 8d25041
Apply suggestions from code review
SUMUKHA-PK 01d0c32
Apply suggestions from code review
SUMUKHA-PK d354ab9
Apply suggestions from code review
SUMUKHA-PK 2e71890
Merge branch 'master' into Consensus-protocol-Design-Doc
SUMUKHA-PK 2a8c4d9
Update Consensus-Protocol.md
SUMUKHA-PK c32828c
Update Consensus-Protocol.md
SUMUKHA-PK 6815e8c
Update Consensus-Protocol.md
SUMUKHA-PK 281906e
Update doc/internal/consensus/Consensus-Protocol.md
SUMUKHA-PK b180d33
Update doc/internal/consensus/Consensus-Protocol.md
SUMUKHA-PK 981d873
Merge branch 'master' into Consensus-protocol-Design-Doc
SUMUKHA-PK fd1f272
Update Consensus-Protocol.md
SUMUKHA-PK a16b909
Update Consensus-Protocol.md
SUMUKHA-PK c312812
Merge branch 'master' into Consensus-protocol-Design-Doc
tpdenk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| # The consensus | ||
|
|
||
| Maintaining consensus is one of the major parts of a distributed system. To know to have achieved a stable system, we need the following two parts of implementation. | ||
|
|
||
| ## The Raft protocol | ||
|
|
||
|
|
||
| ## A strict testing mechanism | ||
|
|
||
| The testing mechanism to be implemented will enable us in figuring out the problems existing in the implementation leading to a more resilient system. | ||
| We have to test for the following basic failures: | ||
| 1. Network partitioning. | ||
| 2. Un-responsive peers. | ||
| 3. Overloading peer. | ||
| 4. Corruption of data in transit. | ||
|
|
||
| ## Graceful handling of failures | ||
|
|
||
| Accepting failures exist and handling them gracefully enables creation of more resilient and stabler systems. Having _circuit breakers_, _backoff mechanisms in clients_ and _validation and coordination mechanisms_ are some of the pointers to be followed. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.