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

Investigate stuck / slow range sync on PeerDAS networks #6113

Closed
jimmygchen opened this issue Jul 16, 2024 · 1 comment
Closed

Investigate stuck / slow range sync on PeerDAS networks #6113

jimmygchen opened this issue Jul 16, 2024 · 1 comment
Labels
bug Something isn't working das Data Availability Sampling Networking

Comments

@jimmygchen
Copy link
Member

Description

#6004 fixes a bunch of known issues and Lighthouse is now able to slowly sync with peers, provided that peers are able to respond to data column by range requests. However it's not really reliable and gets "stuck" quite easily, so I suspect there are some other issues out there that haven't been discovered.

I don't have the logs with me now, however it's quite easy to reproduce:

  1. Start a local testnet with the network_params_das_local.yaml config
  2. Stop one Lighthouse node, and wait for 2-3 epochs to make sure it triggers range sync
  3. Start the Lighthouse node, notice that sync gets stuck pretty quickly

This is now a bit harder to test due to #6108 and it might make sense to get to the bottom of that one first, or alternatively we could try to run a testnet with Prysm / Teku, whichever is able to serve the requests.

@jimmygchen jimmygchen added bug Something isn't working das Data Availability Sampling Networking labels Jul 16, 2024
@jimmygchen
Copy link
Member Author

Fixed in #6276

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

No branches or pull requests

1 participant