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 62a7beec21 Merge pull request #780 from ericdmann/769-error-msg-while-testnet-sync 
Change log level to Info when proposal block hashing fails
 		2017-10-24 23:27:20 -04:00
..
test_data update cswal test 2017-10-23 10:03:54 -04:00
types extract some of the consensus types into ./types 2017-10-10 12:39:21 +04:00
README.md some comments 2016-08-09 20:31:53 -04:00
byzantine_test.go [state] expose ChainID and Params 2017-10-16 10:34:02 +04:00
common.go fixes from review 2017-06-28 11:12:45 -04:00
common_test.go update cswal test 2017-10-23 10:03:54 -04:00
mempool_test.go all: no more anonymous imports 2017-10-04 16:40:45 -04:00
reactor.go extract some of the consensus types into ./types 2017-10-10 12:39:21 +04:00
reactor_test.go PrivValidatorFS is like old PrivValidator, for now 2017-09-21 16:46:31 -04:00
replay.go abci.Info takes a struct; less merkleeyes 2017-09-22 11:42:40 -04:00
replay_file.go node: NewNode takes DBProvider and GenDocProvider 2017-09-21 15:54:33 -04:00
replay_test.go Merge pull request #768 from tendermint/feature/merkleeyes-to-iavl 2017-10-23 11:07:21 -04:00
state.go Merge pull request #780 from ericdmann/769-error-msg-while-testnet-sync 2017-10-24 23:27:20 -04:00
state_test.go [state] expose ChainID and Params 2017-10-16 10:34:02 +04:00
ticker.go consensus: more comments 2017-07-20 00:59:28 -04:00
version.go all: no more anonymous imports 2017-10-04 16:40:45 -04:00
wal.go all: no more anonymous imports 2017-10-04 16:40:45 -04: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.