You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Ethan Buchman
206d00ed8c
|
8 years ago | |
|---|---|---|
| .. | ||
| README.md | 9 years ago | |
| common.go | 9 years ago | |
| common_test.go | 8 years ago | |
| height_vote_set.go | 9 years ago | |
| height_vote_set_test.go | 9 years ago | |
| log.go | 9 years ago | |
| mempool_test.go | 9 years ago | |
| reactor.go | 8 years ago | |
| replay.go | 8 years ago | |
| replay_test.go | 8 years ago | |
| state.go | 8 years ago | |
| state_test.go | 8 years ago | |
| version.go | 9 years ago | |
| wal.go | 8 years ago | |
| wal_test.go | 9 years ago | |
README.md
The core consensus algorithm.
- state.go - The state machine as detailed in the whitepaper
- reactor.go - A reactor that connects the state machine to the gossip network
Go-routine summary
The reactor runs 2 go-routines for each added peer: gossipDataRoutine and gossipVotesRoutine.
The consensus state runs two persistent go-routines: timeoutRoutine and receiveRoutine. Go-routines are also started to trigger timeouts and to avoid blocking when the internalMsgQueue is really backed up.
Replay/WAL
A write-ahead log is used to record all messages processed by the receiveRoutine, which amounts to all inputs to the consensus state machine: messages from peers, messages from ourselves, and timeouts. They can be played back deterministically at startup or using the replay console.