Files
tendermint/consensus
2016-11-15 18:37:00 -05:00
..
2016-10-30 03:55:27 -07:00
2016-10-10 03:10:29 -04:00
2016-11-15 18:34:58 -05:00
2016-10-10 17:05:50 -04:00
2016-08-09 20:31:53 -04:00
2016-10-30 03:55:27 -07:00
2016-11-15 18:34:58 -05:00
2016-08-05 19:15:14 -04:00
2016-10-30 03:55:27 -07:00

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.