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

Not producing block because node didn't wake up within 500ms of the slot time. #2658

Closed
abitmore opened this issue Jul 18, 2018 · 2 comments
Closed

Comments

@abitmore
Copy link
Contributor

Log:

2018-07-18T18:58:27 th_a:invoke handle_block handle_block ] Got 34 trx on block 24291322 by someguy123 -- 400 ms application.cpp:514
2018-07-18T18:58:34 th_a:invoke handle_block handle_block ] Got 29 trx on block 24291323 by aggroed -- 4468 ms application.cpp:514
2018-07-18T18:58:34 th_a:Witness Block Production block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time. witness_plugin.cpp:624
2018-07-18T18:58:35 th_a:Witness Block Production block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time. witness_plugin.cpp:624
2018-07-18T18:58:36 th_a:invoke handle_block handle_block ] Got 56 trx on block 24291324 by ausbitbank -- 855 ms application.cpp:514

Possible scenario:

  • a block arrived with high latency
  • before it arrived, my node didn't try to produce a block (perhaps because it's not its turn?)
  • after it arrived (witness list reshuffled or somehow?), my node suddenly found it's its turn to produce next block, however, it's already in the 2nd second, so it tried twice to produce a block
  • the result (fail) was guaranteed by this code (time diff was always more than 500ms on the 2nd and 3rd try):

if( llabs((scheduled_time - now).count()) > fc::milliseconds( 500 ).count() )
{
capture("scheduled_time", scheduled_time)("now", now);
return block_production_condition::lag;
}

@mvandeberg
Copy link
Contributor

What version of steemd did this happen on?

@abitmore
Copy link
Contributor Author

Was on 0.19.5. Although in OP the quoted code is master branch.

@mac128k mac128k assigned goldibex and unassigned youkaicountry Aug 14, 2018
@mac128k mac128k assigned rajatsteemit and unassigned goldibex Aug 28, 2018
rajatsteemit added a commit that referenced this issue Aug 29, 2018
…500ms), to avoid witness not producing the block during his slot time. This problem is due to arrival of high latency block just before the witness schedule slot time.

Fix for Issue #2658
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants