tendermint/consensus
Ethan Buchman b1cd677711 types: valSet LastProposer->Proposer and Proposer()->GetProposer() 2017-03-05 23:28:42 -05:00
..
test_data consensus: handshake replay test using wal 2017-02-17 19:12:05 -05:00
README.md some comments 2016-08-09 20:31:53 -04:00
byzantine_test.go log warning if peer send failed (Refs #174) 2017-02-21 11:57:33 +04:00
common.go fixes from review 2016-12-22 22:03:42 -05:00
common_test.go consensus: handshake replay test using wal 2017-02-17 19:12:05 -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 fix race 2017-03-05 03:40:36 -05:00
reactor.go remove warning messages in favor of "Send failed" 2017-02-21 13:25:16 +04:00
reactor_test.go TMSP -> ABCI 2017-01-12 15:53:32 -05:00
replay.go test/docker: install abci apps first 2017-03-05 14:59:02 -05:00
replay_file.go move handshake to consensus package 2017-02-20 19:52:36 -05:00
replay_test.go consensus: more handshake replay tests 2017-02-20 21:45:53 -05:00
state.go types: valSet LastProposer->Proposer and Proposer()->GetProposer() 2017-03-05 23:28:42 -05:00
state_test.go types: valSet LastProposer->Proposer and Proposer()->GetProposer() 2017-03-05 23:28:42 -05:00
ticker.go consensus: let time.Timer handle non-positive durations 2017-01-11 10:24:40 -05:00
version.go version bump and release branch 2016-08-05 19:15:14 -04:00
wal.go consensus: handshake replay test using wal 2017-02-17 19:12:05 -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.