Rejecting post-consensus messages because no decided value, dropping the message
Closed this issue · 0 comments
y0sher commented
Description
In CommitteeRunner
We have witnessed that sometimes, a commit quorum is achieved on some nodes and they are sending post-consensus right away, though our node haven't received or processed the last commit message yet and processes the post-consensus before, ending up throwing it away because there is no decided value yet.
Task
Filter the messages out of the queue and don't pop post-consensus messages before we have decided value.