Zach 2cc63069c6 | 7 years ago | |
---|---|---|
.. | ||
test_data | 7 years ago | |
types | 7 years ago | |
README.md | 8 years ago | |
byzantine_test.go | 7 years ago | |
common_test.go | 7 years ago | |
mempool_test.go | 7 years ago | |
reactor.go | 7 years ago | |
reactor_test.go | 7 years ago | |
replay.go | 7 years ago | |
replay_file.go | 7 years ago | |
replay_test.go | 7 years ago | |
state.go | 7 years ago | |
state_test.go | 7 years ago | |
ticker.go | 7 years ago | |
version.go | 7 years ago | |
wal.go | 7 years ago | |
wal_fuzz.go | 7 years ago | |
wal_generator.go | 7 years ago | |
wal_test.go | 7 years ago |
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.
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.