-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[CRDT] Reconnecting a peer causes issues receiving deltas and sending out pins #798
Comments
After restarting the out-of-sync peer again but with the |
so checking back after fixing my test setup and this one is still broken. |
The two in-sync peers don't even think that the out-sync-peer should be pinning any of the pins... |
#792 should have made that a peer in the trusted peerset should only have to bootstrap once when using CRDT consensus. |
Not sure what that means. If Let's discuss about this during standup. I am seeing the "getting root delta" error by default and other peers cannot sync at all because they cannot even get the root so things don't work for me. |
ok I found an issue (the issue probably) |
Bitswap needs to exist before connections are opened! Fixes #798
Additional information:
Describe the bug:
Three peer cluster, two peers bootstrapped to the first peer. Shutdown 2nd peer and then start again without
--bootstrap
as the trusted peersPeerInfo
should now be in the peerstore and it will connect to those peers when it starts back up. This worked fine, confirmed with apeers ls
against the restarted peer. The issue occurred when pin operations against the first peer started.The following is an excerpt of the logs from the restarted peer:
If you
ipfs-cluster-ctl add <file>
from the out-of-sync peer, it will attempt to pin on all the peers but at theheight
of the out-of-sync peer, though it doesn't succed:It appears that the out-of-sync peer never recovers...
The text was updated successfully, but these errors were encountered: