Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beacon client stalls during init-sync to sync transition #4582

Closed
torfbolt opened this issue Jan 18, 2020 · 5 comments
Closed

Beacon client stalls during init-sync to sync transition #4582

torfbolt opened this issue Jan 18, 2020 · 5 comments
Labels
Bug Something isn't working

Comments

@torfbolt
Copy link

Sometimes the transition from init-sync to normal sync seems to silently fail. I saw this particularly when the client went into init-sync mode to resync after falling behind:

time="2020-01-18 18:32:50" level=info msg="Processing block 63154/63164 - estimated time remaining 20s" blocksPerSecond=0.5 peers="1/10" prefix=initial-sync
time="2020-01-18 18:32:50" level=info msg="Executing state transition on block" prefix=forkchoice root=0x2e721142... slot=63154
time="2020-01-18 18:32:52" level=info msg="Finished applying state transition" attestations=5 deposits=0 prefix=blockchain slot=63154
time="2020-01-18 18:32:52" level=info msg="Resync attempt complete" prefix=initial-sync slot=63154 synced=true
time="2020-01-18 18:33:13" level=info msg="Peer disconnected" active=9 peer=16Uiu2HAmEhpnUJhpdzpiduRRrRCkpQAGZsUq3qJmWpvbdzFUWdeJ prefix=p2p
time="2020-01-18 18:36:15" level=info msg="Peer connected" active=10 peer=16Uiu2HAkvSZyPFfSonVPiF9EEPKKv65v6QcPC3sBgPVRxURWX2u3 prefix=p2p
time="2020-01-18 18:40:22" level=info msg="Peer disconnected" active=9 peer=16Uiu2HAkwSeLfRR7m7zxpF3qxDwGK8ghHizJDHDd2e6j8arwsNG1 prefix=p2p
time="2020-01-18 18:48:47" level=info msg="Peer connected" active=10 peer=16Uiu2HAmRMqPe1nR1yAwUEpBKzUh8ABHzcMBSRnnK1z4fkuARu8e prefix=p2p
time="2020-01-18 18:48:47" level=info msg="Peer disconnected" active=9 peer=16Uiu2HAmRMqPe1nR1yAwUEpBKzUh8ABHzcMBSRnnK1z4fkuARu8e prefix=p2p
time="2020-01-18 18:49:18" level=info msg="Fallen behind peers; reverting to initial sync to catch up" currentEpoch=1976 peersEpoch=1974 prefix=sync syncedEpoch=1973
time="2020-01-18 18:51:10" level=info msg="Peer connected" active=10 peer=16Uiu2HAmEhpnUJhpdzpiduRRrRCkpQAGZsUq3qJmWpvbdzFUWdeJ prefix=p2p
time="2020-01-18 18:58:33" level=info msg="Peer connected" active=11 peer=16Uiu2HAmRMqPe1nR1yAwUEpBKzUh8ABHzcMBSRnnK1z4fkuARu8e prefix=p2p
time="2020-01-18 18:59:28" level=info msg="Peer disconnected" active=9 peer=16Uiu2HAmEhpnUJhpdzpiduRRrRCkpQAGZsUq3qJmWpvbdzFUWdeJ prefix=p2p

It looks like the client tries to resync again, but no block processing occurs any more, only some p2p log messages. After a restart the client usually syncs ok again.

@torfbolt
Copy link
Author

Possibly related to #4551 ?

@mcdee
Copy link
Contributor

mcdee commented Jan 18, 2020

#4551 became a bit too unfocused, #4570 should address this issue.

@torfbolt
Copy link
Author

I just noticed that the beacon client uses 3.8 of my 4G RAM, which would explain random stalling. Is it supposed to use that much or is there a memory leak/issue?

@0xKiwi 0xKiwi added the Bug Something isn't working label Jan 26, 2020
@rauljordan
Copy link
Contributor

Hey @torfbolt we just resolved this thanks @nisdas in #4811, could you try again?

@prestonvanloon
Copy link
Member

FYI #4811 was reverted in #4825

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants