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
{{ message }}
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: