You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 2, 2021. It is now read-only.
when we restart a swarm node the kademlia table's connection changes - nodes which are known about and that were with established connections to us are not prioritized over other nodes.
this, in turn, incurs a big traffic load as a node suddenly has to push for example half of its chunks (bin 0) to all of the new peers in bin 0
this is easily reproducible when running a persistent cluster, shutting it down, then starting the nodes again.
we should prioritize known peers when reconnecting
when we restart a swarm node the kademlia table's connection changes - nodes which are known about and that were with established connections to us are not prioritized over other nodes.
this, in turn, incurs a big traffic load as a node suddenly has to push for example half of its chunks (bin 0) to all of the new peers in bin 0
this is easily reproducible when running a persistent cluster, shutting it down, then starting the nodes again.
we should prioritize known peers when reconnecting