mirror of https://github.com/tendermint/tendermint.git synced 2026-01-09 14:43:19 +00:00

Files

Anton Kalyaev 3308ac7d83 set skip_timeout_commit to true for tests

For the tests its better to not use the timeout_commit, and to wait for all the
votes, because otherwise we can end up with timing dependencies in the testing
code which can lead to nondeterministic failures. That was part of the reason
for this change originally.

2017-01-11 18:00:26 -05:00

test_data

consensus: let time.Timer handle non-positive durations

2017-01-11 10:24:40 -05:00

byzantine_test.go

consensus: check HasAll when TwoThirdsMajority

2017-01-11 17:53:46 -05:00

common_test.go

consensus: check HasAll when TwoThirdsMajority

2017-01-11 17:53:46 -05:00

common.go

fixes from review

2016-12-22 22:03:42 -05:00

height_vote_set_test.go

Fixing issues from review in #229

2016-11-15 18:48:35 -05:00

height_vote_set.go

Fix BFT issue where VoteSetMaj23Message wasn't being sent where prs.Round == blockStore.Round()

2016-11-15 18:48:35 -05:00

log.go

Make consensus logs use default log handler

2015-12-21 17:26:08 -08:00

mempool_test.go

fixes

2016-11-16 13:25:13 -05:00

reactor_test.go

set skip_timeout_commit to true for tests

2017-01-11 18:00:26 -05:00

reactor.go

Fix #341

2017-01-11 08:57:10 -08:00

README.md

some comments

2016-08-09 20:31:53 -04:00

replay_test.go

fixes from review

2016-12-22 22:03:42 -05:00

replay.go

consensus: let time.Timer handle non-positive durations

2017-01-11 10:24:40 -05:00

state_test.go

MakePartSet takes partSize from config. fix replay test

2016-11-16 01:23:16 -05:00

state.go

make progress asap on full precommit votes optional (Refs #348 )

2017-01-11 18:00:26 -05:00

ticker.go

consensus: let time.Timer handle non-positive durations

2017-01-11 10:24:40 -05:00

version.go

version bump and release branch

2016-08-05 19:15:14 -04:00

wal.go

consensus: sync wal.writeHeight

2016-12-22 15:01:02 -05: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.