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
IPFS not announcing CIDs on indirect peers #10266
Comments
@iumarabbas can you show please |
@Jorropo - Please see the response for both ipfs stats dht and ipfs swarm peers
All the nodes are connected through public IP and accessible publicly and the swarm key is same. [ NodeB <--> NodeA ] <==>[ Node0 <--> Node3 ] The nodes are hosted on azure cloud services: NodeB and NodeA are in virtual network 1. NodeB:ipfs stats dht DHT wan (0 peers): ipfs swarm peers NodeAroot@nodeA:/home/ssiadmin# ipfs stats dht Error: no LAN client found Node0root@node0:/home/ssiadmin# ipfs stats dht Error: no LAN client found Node3root@node3:/home/ssiadmin# ipfs stats dht Error: no LAN client found |
@iumarabbas the issue here is that the accelerated dht client is constantly failing to crawl your network, so it has no peer to issue queries to. It could also be that it hasn't finished yet however I would find that weird given your network is so slow it should crawl it in no times. |
@Jorropo - As we are using Azure Cloud network so the network bandwidth/speed should not have issue here appearantly. We are getting the following response to the above query:
|
Next steps would be to capture jaeger traces of the DHT to see what it is doing. |
@Jorropo Judging from the documentation https://github.com/ipfs/kubo/blob/master/docs/experimental-features.md#private-networks . IPFS private network is an experimental feature. I suppose it's still not stable enough to be used for heavy load production environments P.S: Same project as @iumarabbas |
@mzuhaq7 it is the inverse problem, we struggle on small networks, if your network is bigger (and is mainly routed over WAN) it should work like the amino network. |
@Jorropo I see. I tested it out on a network of 6 nodes but files were not being fetched from indirect nodes. I doubt if i increase network size more that'll help. Is this a known issue in private IPFS? This seems to be a very basic functionality that should be working fine. We followed the simple steps to setup a private IPFS network here https://medium.com/@s_van_laar/deploy-a-private-ipfs-network-on-ubuntu-in-5-steps-5aad95f7261b I see similar issues reported with no solution |
Checklist
Installation method
built from source
Version
Config
Description
I have four nodes NodeB, NodeA, Node0, and Node3
NodeB is peer of NodeA,
NodeA is peer of NodeB and Node0
Node0 is a peer of NodeA and Node3
Node3 is a peer of Node3
When I upload file on NodeB it is accessible on NodeA but not on Node0 and Node3 as these nodes are not directly added as peer but have same swarm key. what might be the reason?
I have configured all nodes as dhtserver and turned the dht server check to “active” but its not working.
When we get content from direct peer node, content is retrieved but for indirect peer the content is not accessible directly.
The text was updated successfully, but these errors were encountered: