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

One minute between these 2 blocks #1

Closed
botstorm opened this issue May 20, 2019 · 3 comments
Closed

One minute between these 2 blocks #1

botstorm opened this issue May 20, 2019 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@botstorm
Copy link

we finished test and chain is slow. here is some log with no transactions over network
[2019-05-15 23:33:37.023910] [0x00007f14af928700] [debug] Normal: nothing to do with transactions packet in this state
[2019-05-15 23:33:37.023925] [0x00007f14af928700] [debug] TRANSPORT> POSTPHONED finished, round 2398489
[2019-05-15 23:34:22.480128] [0x00007f14af928700] [debug] TRANSPORT> Got SS Last Block: 2398488
[2019-05-15 23:34:26.502397] [0x00007f14af928700] [warning] -----------------------------------------------------------
[2019-05-15 23:34:26.502491] [0x00007f14af928700] [warning] NODE> BigBang #2398489: last written #2398488, current #2398489
[2019-05-15 23:34:26.502546] [0x00007f14af928700] [warning] -----------------------------------------------------------

here one minute between these 2 blocks

@kondrashovsv kondrashovsv changed the title Test One minute between these 2 blocks May 20, 2019
@kondrashovsv
Copy link
Member

kondrashovsv commented May 20, 2019

I also have
image

@kondrashovsv kondrashovsv added bug 🪲 Something isn't working help wanted Extra attention is needed and removed bug 🪲 Something isn't working labels May 20, 2019
@micmac0
Copy link

micmac0 commented May 23, 2019

I also have
image

About this graph here are test conditions we had :
3 nodes configured to receive each less than 300tps. These 3 nodes were configured to participate in consensus. (delay set to 3ms between each trx and we need to count connexion cost from client to node)
That s why we clearly see some level when we added removed nodes.
Around 8h20 we started to see some delay. When some nodes in network can t manage to deal with too much load, blocks start to have round number of transactions such as 800 1000 2000 4000 or number like that. When all is ok number are much more random like 478 832 ...

@ghost
Copy link

ghost commented Jun 4, 2019

During the last 2 weeks, after updating the client this error could not be reproduced.

@ghost ghost closed this as completed Jun 4, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants