-
Notifications
You must be signed in to change notification settings - Fork 40
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
Skaled sleeps for empty block interval during catchup under load #1560
Comments
skaled: 3.17.0-beta.3 |
Network: Regressions
|
skaled: 3.17.0-beta.4 |
Not solved in 3.17.0-beta.4 skaled couldn't reach actual block number due load (10 tx per block, block mining time = 3-4 seconds)
|
It is strange it is giving very small number of blocks per catchup It should give more blocks. There is a bug somewhere. How large is each transaction in bytes? |
Probably, all incoming transactions go to future queue. Also, I'd suggest to check if consensus can create latest blocks by processing received earlier consensus messages, and not catch-up |
Reopening this bug and moving it to 2.3 as there may be some slow cases remaining but they are non-critical |
Closed as fixed. Slow catcup will be fixed in #1640 |
Description:
Skaled on updated node stuck because of #1558 and starting catching up and never reaching the actual block.
Preconditions:
Active schain medium type with MTM
Versions:
15 nodes with 3.16.1 (2.1.1 release)
1 node with schain:3.17.0-beta.1 (2.2 release)
To Reproduce
Expected behavior
Skaled should catching up with blocks faster rather than new blocks being mined
Actual state
10-12 blocks catching up in 15-30 seconds
Logs:
skaled_slow_catchup.log
The text was updated successfully, but these errors were encountered: