Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

DAWN-492 ⁃ Not producing block because node didn't wake up within 500ms of the slot time. #397

Closed
pavybez opened this issue Sep 11, 2017 · 6 comments
Closed

DAWN-492 ⁃ Not producing block because node didn't wake up within 500ms of the slot time. #397

pavybez opened this issue Sep 11, 2017 · 6 comments
Labels
track-in-jira
Milestone
Q1, 2018

Comments

@pavybez
Copy link

pavybez commented Sep 11, 2017 •
edited by blockone-syncclient

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
@pavybez
Copy link
Author

pavybez commented Sep 11, 2017

Attached is the config.ini of the eosd.

config.txt

@bytemaster
Copy link
Contributor

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 wanderingbort added this to the EOS Dawn 2.0 milestone Sep 12, 2017
@wanderingbort
Copy link
Contributor

We are planning to address this issue in the EOS Dawn 2.0 milestone as part of #301

@bytemaster bytemaster modified the milestones: EOS Dawn 1.1, EOS Dawn 2.0 Sep 13, 2017
@brianjohnson5972
Copy link
Contributor

@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?

@Aspian123 Aspian123 modified the milestones: EOS Dawn 1.1, EOS Dawn 2.0 Nov 1, 2017
@heifner heifner modified the milestones: EOS Dawn 2.0, EOS Dawn 3.0 Nov 6, 2017
@blockone-syncclient blockone-syncclient changed the title 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. Jan 16, 2018
@blockone-syncclient
Copy link

➤ Corey Lederer commented:

Related to GH301 / DAWN‌-491

@heifner
Copy link
Contributor

heifner commented Jan 24, 2018

This will be worked under #301

@heifner heifner closed this as completed Jan 24, 2018
taokayan pushed a commit to taokayan/eos that referenced this issue May 15, 2019
@larryk85
Merge pull request EOSIO#397 from EOSIO/docs/upgrade-instructions
1f68458 
Add "upgrading" directory to docs
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
track-in-jira
Projects
None yet
Milestone
Q1, 2018
Development

No branches or pull requests
8 participants
@bytemaster @wanderingbort @heifner @pavybez @brianjohnson5972 @Aspian123 @coreylederer @blockone-syncclient