You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
…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
Log:
Possible scenario:
steem/libraries/plugins/witness/witness_plugin.cpp
Lines 702 to 706 in 1b53cf6
The text was updated successfully, but these errors were encountered: