2016-09-09 23:50:25 -04:00
..
2016-08-17 23:08:43 -04:00
2016-08-09 20:31:53 -04:00
2016-09-09 23:50:25 -04:00
2016-08-05 19:15:14 -04:00
2016-07-11 22:37:39 -04:00
2016-08-17 23:08:43 -04: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.