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.

Sign up for GitHub

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

Jump to bottom

bug(discovery): discovery is unable to find all full nodes via dht lookup #3573

Open
walldiss opened this issue Jul 18, 2024 · 1 comment
Open

bug(discovery): discovery is unable to find all full nodes via dht lookup #3573

walldiss opened this issue Jul 18, 2024 · 1 comment
Assignees
@walldiss @renaynay
Labels
area:p2p bug Something isn't working enhancement New feature or request

Comments

@walldiss
Copy link
Member

Implementation ideas

I've conducted multiple tests to gather detailed information on the number of full nodes (FN) currently active within the network. The results indicate that the actual number of active nodes is significantly lower than expected. Below are the details of the nodes observed during the tests on both the Mocha and Mainnet environments:

Mocha Network:

Full Nodes: 54
Archival Nodes: 12

Mainnet:

Full Nodes: 17
Archival Nodes: 1

This discrepancy suggests there may be an underlying issue related to querying or persisting DHT records. It's crucial to investigate whether this is an isolated incident or a widespread problem affecting the network's reliability and data accessibility.
@walldiss walldiss added enhancement New feature or request area:p2p labels Jul 18, 2024
@walldiss walldiss self-assigned this Jul 18, 2024
@walldiss
Copy link
Member Author

Additionally, we have shrexSub, that also monitors amount of full nodes within active connections. Mainnet metrics for 3 nodes suggests that there are 100+ FN connected for each reporting node.
image

@renaynay renaynay added the bug Something isn't working label Jul 18, 2024
@renaynay renaynay self-assigned this Jul 18, 2024
@renaynay renaynay mentioned this issue Jul 24, 2024
Merged
Wondertan pushed a commit that referenced this issue Jul 24, 2024
@renaynay
fix(nodebuilder/p2p): LNs restricted to acting as DHT clients *only* (#…
4b2f507 
…3590)

Resolves #3574

Potentially targets #3573
Wondertan pushed a commit that referenced this issue Jul 24, 2024
@renaynay @Wondertan
fix(nodebuilder/p2p): LNs restricted to acting as DHT clients *only* (#…
6549873 
…3590)

Resolves #3574

Potentially targets #3573
sebasti810 pushed a commit to sebasti810/celestia-node that referenced this issue Aug 14, 2024
@renaynay @sebasti810
fix(nodebuilder/p2p): LNs restricted to acting as DHT clients *only* (c…
c1b6d74 
…elestiaorg#3590)

Resolves celestiaorg#3574

Potentially targets celestiaorg#3573
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@walldiss walldiss

@renaynay renaynay

Labels
area:p2p bug Something isn't working enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@walldiss @renaynay