Author | SHA1 | Message | Date |
---|---|---|---|
Marko | fa3287c012 |
maverick: reduce some duplication (#6052)
- Reduce duplication in messages and metrics. - merge WAL interfaces. Meant to push the developer to make changes in both places. |
4 years ago |
Callum | a2a6852ab9 |
use correct source of evidence time
Conflicting votes are now sent to the evidence pool to form duplicate vote evidence only once the height of the evidence is finished and the time of the block finalised. |
4 years ago |
Anton Kaliaev |
b1328db07f
|
modify Reactor priorities (#5826) (#5830)
blockchain/vX reactor priority was decreased because during the normal operation (i.e. when the node is not fast syncing) blockchain priority can't be the same as consensus reactor priority. Otherwise, it's theoretically possible to slow down consensus by constantly requesting blocks from the node. NOTE: ideally blockchain/vX reactor priority would be dynamic. e.g. when the node is fast syncing, the priority is 10 (max), but when it's done fast syncing - the priority gets decreased to 5 (only to serve blocks for other nodes). But it's not possible now, therefore I decided to focus on the normal operation (priority = 5). evidence and consensus critical messages are more important than the mempool ones, hence priorities are bumped by 1 (from 5 to 6). statesync reactor priority was changed from 1 to 5 to be the same as blockchain/vX priority. Refs https://github.com/tendermint/tendermint/issues/5816 |
4 years ago |
Tess Rinearson | 0d9606e1b4 |
reactors: omit incoming message bytes from reactor logs (#5743)
After a reactor has failed to parse an incoming message, it shouldn't output the "bad" data into the logs, as that data is unfiltered and could have anything in it. (We also don't think this information is helpful to have in the logs anyways.) |
4 years ago |
Callum Waters | 9d354c842e | evidence: structs can independently form abci evidence (#5610) | 4 years ago |
Callum Waters | dacbfbe1fe | test: add evidence e2e tests (#5488) | 4 years ago |