-
Notifications
You must be signed in to change notification settings - Fork 110
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
Bitswap.GetBlockRequest retrieval is extremely slow. #316
Comments
|
It is the same even if you use Level-DB.
I have discovered one thing. In more detail, the websocket bootstrap node is behind nginx-ingress. Therefore, the Advertise Address and the actual connection address are different. |
This was my mistake. The cause was that the ipfs-cluster was configured incorrectly and the pin was not pinned. |
Client has only one Bootstrap node connected to it.
Interestingly, even if the PeerId is different, the CID requested from the same IP is quickly received.
(Block is not stored locally, I used InMemoryDatastore.)
In the log below QmZe65rbJhncNTmaCXMq54FRG69hgJZodyorLKVmBCX2Sx is taking very long. However, the CID can be immediately obtained from the bootstrap node.
Bootstrap node's swarm streams:
Similar Possible Issues: ipfs/kubo#8346
Bootstrap Node:
ipfs version 0.19.2
Client:
github.com/ipfs/boxo v0.8.0
The text was updated successfully, but these errors were encountered: