certusone
/
tendermint
mirror of https://github.com/certusone/tendermint.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
tendermint/consensus
History
Jae Kwon 655d829314 Fix proposal sign bytes. Start tracking blockID in POL 2016-11-15 18:35:17 -05:00
..
test_data cswal -> cs_wal_dir 2016-10-30 03:55:27 -07:00
README.md some comments 2016-08-09 20:31:53 -04:00
common.go type safe events 2016-10-10 03:10:29 -04:00
common_test.go Fix proposal sign bytes. Start tracking blockID in POL 2016-11-15 18:35:17 -05:00
height_vote_set.go Fix proposal sign bytes. Start tracking blockID in POL 2016-11-15 18:35:17 -05:00
height_vote_set_test.go Use BlockID everywhere 2016-11-15 18:34:58 -05:00
log.go Make consensus logs use default log handler 2015-12-21 17:26:08 -08:00
mempool_test.go add test for mempool deadlock 2016-10-10 17:05:50 -04:00
reactor.go Fix proposal sign bytes. Start tracking blockID in POL 2016-11-15 18:35:17 -05:00
replay.go Use BlockID everywhere 2016-11-15 18:34:58 -05:00
replay_test.go cswal -> cs_wal_dir 2016-10-30 03:55:27 -07:00
state.go Fix proposal sign bytes. Start tracking blockID in POL 2016-11-15 18:35:17 -05:00
state_test.go Fix proposal sign bytes. Start tracking blockID in POL 2016-11-15 18:35:17 -05:00
version.go version bump and release branch 2016-08-05 19:15:14 -04:00
wal.go cswal -> cs_wal_dir 2016-10-30 03:55:27 -07: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.