Trinity times out peer connections during state sync
See original GitHub issueWhat is wrong?
While resuming state sync my node stalled while processing something.
Here are the logs: https://gist.githubusercontent.com/pipermerriam/f33802d8d8890af3c6c7a128e2745e75/raw/d83f3abefabeb3dcef5e6d12518db1755f66b666/trinity-state-sync-stalled.log
Event occured between timestamps 07-23 21:20:34
and 07-23 21:21:28
(approximately a full minute of dead time.
How can it be fixed
See what blocked the process for so long and figure out how to move it into a process pool executor or something.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Release Notes — trinity 0.1.0-alpha.37 documentation
During Beam Sync, Trinity now collects account data that is not touched by active blocks. We often call this “state backfill”. Obtaining the...
Read more >Aurora-Trinity: A Super-Light Client for Distributed Ledger ...
Initial synchronization with the network can take a long time due to ledger size and its continuous growth [3]. In January 2020 ...
Read more >Intro to Beam Sync
So we must ask peers for trie nodes one at a time. In contrast, Fast Sync can ask peers for up to 384...
Read more >Trinity Release 3.12.x Command Line Reference Guide
The terms Trinity and ForeFront are trademarks of Patton ... 57 Secure Real-Time Protocol (SRTP) Configuration . ... State Profiles.
Read more >ethereum/trinity
Until sync is finished trinity won't bother requesting transactions itself AFAIK; but many peers send them proactively, so you should see those (if...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think this has a good description of the issue itself (i.e. the observed behaviour we want to change), and in the PR we can discuss how we’ll fix it
@gsalgado do you want to keep this open? I think I’d prefer a new issue more specific to what you are working on in #1124