certusone
/
tendermint
mirror of https://github.com/certusone/tendermint.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
tendermint/consensus
History
Ethan Buchman c9698e4848 fixes from review 2016-12-22 22:03:42 -05:00
..
test_data test: automate building consensus/test_data 2016-12-18 00:15:10 -05:00
README.md some comments 2016-08-09 20:31:53 -04:00
byzantine_test.go consensus: TimeoutTicker, skip TimeoutCommit on HasAll 2016-12-19 15:42:36 -05:00
common.go fixes from review 2016-12-22 22:03:42 -05:00
common_test.go fixes from review 2016-12-22 22:03:42 -05:00
height_vote_set.go Fix BFT issue where VoteSetMaj23Message wasn't being sent where prs.Round == blockStore.Round() 2016-11-15 18:48:35 -05:00
height_vote_set_test.go Fixing issues from review in #229 2016-11-15 18:48:35 -05:00
log.go Make consensus logs use default log handler 2015-12-21 17:26:08 -08:00
mempool_test.go fixes 2016-11-16 13:25:13 -05:00
reactor.go consensus: no internal vars in reactor.String() 2016-12-20 00:17:37 -05:00
reactor_test.go fixes from review 2016-12-22 22:03:42 -05:00
replay.go consensus: mv timeoutRoutine into TimeoutTicker 2016-12-19 22:29:32 -05:00
replay_test.go fixes from review 2016-12-22 22:03:42 -05:00
state.go consensus: mv timeoutRoutine into TimeoutTicker 2016-12-19 22:29:32 -05:00
state_test.go MakePartSet takes partSize from config. fix replay test 2016-11-16 01:23:16 -05:00
ticker.go consensus: mv timeoutRoutine into TimeoutTicker 2016-12-19 22:29:32 -05:00
version.go version bump and release branch 2016-08-05 19:15:14 -04:00
wal.go consensus: wal.Flush() and cleanup replay tests 2016-12-17 23:43:17 -05:00

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.