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

DAWN-274 ⁃ eosd sync issues for hotfix 1 #903

Closed
blockone-syncclient opened this issue Dec 8, 2017 · 2 comments
Closed

DAWN-274 ⁃ eosd sync issues for hotfix 1 #903

blockone-syncclient opened this issue Dec 8, 2017 · 2 comments
Assignees
Milestone

Comments

@blockone-syncclient
Copy link

blockone-syncclient commented Dec 8, 2017

Phil has been working on some sync issues for the december hotfix #1
On Dec. 7, testnet B node 4 went out of sync. several attempts to restart it proved problematic as the sync feature continually got out-of-order blocks, or in some cases simply stopped dead.

After log analysis, code review, and localized testing, It was determined that the sync manager object was still requesting concurrent sets of blocks from multiple peers, rather than the intended behavior of receiving one chunk at a time but varying the intended requester so as to avoid excessive burden to a single peer.

pmesnier added a commit that referenced this issue Dec 9, 2017
…om only one peer at a time. added more logging too.
heifner added a commit that referenced this issue Dec 9, 2017
@blockone-syncclient
Copy link
Author

➤ Corey Lederer commented:

Phil and I decided to close this and add the description elements directly to STAT-276, as they were overlapping tickets.

@coreylederer
Copy link
Contributor

Closing. This is now a duplicate of #916

spoonincode referenced this issue Dec 11, 2017
@thomasbcox thomasbcox added this to the Q1, 2018 milestone Jan 5, 2018
@blockone-syncclient blockone-syncclient changed the title STAT-274 ⁃ eosd sync issues for hotfix 1 DAWN-274 ⁃ eosd sync issues for hotfix 1 Jan 16, 2018
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants