feat(cometbft): mitigate slow blocks due to inactive validators #1818
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Decreases default cometBFT consensus config param
timeout_propose
from 3s to 1s.This aim to mitigate slow blocks when the proposing validator is offline/inactive. Currently, when 1 of 3 validators are offline, the block times on staging decreases from 1s to 4s.
I had a look at some other cosmos chains and aligning timeout_commit and timeout_propose seems to be common practice:
timeout_commit=200ms, timeout_propose=300s
timeout_commit=1s, timeout_propose=1s
This change aims to mitigate the affect of offline validators on block times.
issue: #1812