tendermint/consensus
Ethan Buchman c90bde3187 some comments 2016-08-09 20:31:53 -04:00
..
README.md some comments 2016-08-09 20:31:53 -04:00
common.go Merge remote-tracking branch 'origin/replay' 2016-01-28 19:53:22 -08:00
common_test.go consensus: t.Fatal -> panic 2016-07-11 22:37:39 -04:00
height_vote_set.go consensus: hvs.Reset(height, valSet) 2016-07-11 22:37:42 -04:00
height_vote_set_test.go consensus: t.Fatal -> panic 2016-07-11 22:37:39 -04:00
log.go Make consensus logs use default log handler 2015-12-21 17:26:08 -08:00
mempool_test.go consensus: increase mempool_test timeout 2016-07-11 22:37:42 -04:00
reactor.go fixes from review 2016-04-26 22:17:13 -04:00
replay.go No global config 2016-05-08 15:00:58 -07:00
replay_test.go consensus: t.Fatal -> panic 2016-07-11 22:37:39 -04:00
state.go some comments 2016-08-09 20:31:53 -04:00
state_test.go crank consensus timeout parameters for tests (see #236) 2016-07-12 14:25:27 -04:00
version.go version bump and release branch 2016-08-05 19:15:14 -04:00
wal.go cswal_light logs own votes; fix tests 2016-04-19 20:45:33 -04:00
wal_test.go consensus: t.Fatal -> panic 2016-07-11 22:37:39 -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.