DAWN-492 ⁃ Not producing block because node didn't wake up within 500ms of the slot time. #397
Description
I started a single node with wall_api_plugin embedded and initiated some transactions using ./eosc benchmark transfer 600 600.
I see the following output in the log file.
2994239ms thread-0 producer_plugin.cpp:210 block_production_loo ] initk generated block #202 @ 2017-09-11T06:49:54 with 0 trxs 0 pending
2998489ms thread-0 producer_plugin.cpp:229 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
3000615ms thread-0 producer_plugin.cpp:229 block_production_loo ] Not producing block because node didn't wake up within 500ms of the slot time.
3002818ms thread-0 chain_controller.cpp:235 _push_block ] inith #203 @2017-09-11T06:50:03 | 0 trx, 0 pending, exectime_ms=13
Activity
pavybez commentedon Sep 11, 2017
Attached is the config.ini of the eosd.
config.txt
bytemaster commentedon Sep 11, 2017
This is an indication that the single CPU is getting backlogged by a large blocking task that is not properly timebound... eg, block generation with a large pending set.
wanderingbort commentedon Sep 12, 2017
We are planning to address this issue in the EOS Dawn 2.0 milestone as part of #301
brianjohnson5972 commentedon Oct 4, 2017
@bytemaster or @coreylederer or @thomasbcox This task is marked as EOS Dawn 1.1, but the above comment indicates that it will be addressed by another issue, that is marked as EOS Dawn 2.0. Should this be closed and/or EOS Dawn 1.1 removed?
[-]Not producing block because node didn't wake up within 500ms of the slot time.[/-][+]DAWN-492 ⁃ Not producing block because node didn't wake up within 500ms of the slot time.[/+]blockone-syncclient commentedon Jan 24, 2018
➤ Corey Lederer commented:
Related to GH301 / DAWN-491
heifner commentedon Jan 24, 2018
This will be worked under #301
Merge pull request EOSIO#397 from EOSIO/docs/upgrade-instructions