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 c0e2649ed6
Merge pull request #788 from tendermint/feature/548-indexing-tags 
new pubsub package
 		2017-11-08 01:02:48 +00:00
..
test_data remove test_data/empty_block and test_data/small_blockN 2017-11-02 13:20:14 -05:00
types copy RoundState for event 2017-11-07 23:57:23 +00:00
README.md
…
byzantine_test.go new pubsub package 2017-10-30 00:32:22 -05:00
common_test.go new pubsub package 2017-10-30 00:32:22 -05:00
mempool_test.go Merge pull request #788 from tendermint/feature/548-indexing-tags 2017-11-08 01:02:48 +00:00
reactor.go Merge pull request #788 from tendermint/feature/548-indexing-tags 2017-11-08 01:02:48 +00:00
reactor_test.go new pubsub package 2017-10-30 00:32:22 -05:00
replay.go new pubsub package 2017-10-30 00:32:22 -05:00
replay_file.go fixes from my own review 2017-10-30 00:32:23 -05:00
replay_test.go new pubsub package 2017-10-30 00:32:22 -05:00
state.go Merge pull request #788 from tendermint/feature/548-indexing-tags 2017-11-08 01:02:48 +00:00
state_test.go new pubsub package 2017-10-30 00:32:22 -05:00
ticker.go
…
version.go
…
wal.go fixes from Bucky's and Emmanuel's reviews 2017-10-30 11:12:01 -05:00
wal_test.go fixes from review 2017-10-25 21:54:56 -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.