-
Notifications
You must be signed in to change notification settings - Fork 221
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
v0.6.1 - Empty DHT routing table #561
Comments
@hsanjuan it's hard to say exactly what the problem is without looking at the test, can you post the link? A diagnostic questions though: are you waiting for the DHTs to be connected to each other (e.g. periodically polling routing table sizes to see if > 1) or doing something racy like Line 700 in 067f8ab
This will inform us whether there's an issue wherein the routing table will never populate. |
Ah, wait... The DHT now defaults to starting in "auto" mode. A DHT node will only transition to server mode if it finds an AutoNAT server that tells it that it's dialable. That's probably your issue. I've filed two related issues: #564, libp2p/go-libp2p-autonat#73. (and I'm going to cut an RC without the mode switching for now) |
Thanks, I'm closing this in favor of the other issues. |
Since v0.6.1 I have a few of my tests are failing because the DHT routing table is empty, therefore discovery does not work any more.
The host setup process is as follows:
host.Connect(...)
to each of the N hostsThe DHTs for each host are created before opening a connection.
Each of the N hosts is expected to be able to find routing to any of the others, with discovery happening via the DHT.
The routing table should have received 1 entry upon Connect and therefore auto-discovered everyone else on the first routing table refresh. However, this refresh is having no effect. Logs show how the refresh fails:
This worked in v0.5.2. Any ideas on why there are no peers in the routing table when one peer has opened a connection?
The text was updated successfully, but these errors were encountered: