Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

consensus: set last_block_index during CheckCommits #1960

Conversation

AnnaShaleva
Copy link
Member

This commit makes block time closer to the desired MillisecondsPerBlock
value provided via node configuration. It also allows the node to work
more instead of waiting for a timer.

This PR will close #1959.

@AnnaShaleva AnnaShaleva force-pushed the dbft/set_last_block_time_during_checkcommits branch from 5ba597e to 7f3e00b Compare September 24, 2020 11:14
This commit makes block time closer to the desired MillisecondsPerBlock
value provided via node configuration. It also allows the node to work
more instead of waiting for a timer.
@AnnaShaleva AnnaShaleva force-pushed the dbft/set_last_block_time_during_checkcommits branch from 7f3e00b to 899655a Compare September 25, 2020 07:21
@erikzhang erikzhang merged commit 0e83e75 into neo-project:master Sep 25, 2020
roman-khimov added a commit to nspcc-dev/dbft that referenced this pull request Sep 25, 2020
Make block timing more accurate under load. BlockIndex is needed to
distinguish between consensus-produced block and the one added via regular
block addition mechanism.

See neo-project/neo#1959 and neo-project/neo#1960.
ShawnYun pushed a commit to ShawnYun/neo that referenced this pull request Jan 8, 2021
cloud8little pushed a commit to cloud8little/neo that referenced this pull request Jan 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Compensate for block processing time in DBFT timer
3 participants