This repository has been archived by the owner on May 11, 2022. It is now read-only.
Offload peers supporting AutoNAT to peerstore #9
Milestone
Comments
|
An alternative solution could be #40 (comment). |
This was referenced Feb 26, 2020
willscott
added a commit
that referenced
this issue
Mar 11, 2020
* Single goroutine managing autonat-relevent events. * Watching incoming connections and local interface changes as signals. * Emit a single 'rechabilitychanged' persistent event fix #40 fix #36 fix #35 fix #34 fix #11 obsolete #28 obsolete #9 Co-authored-by: Aarsh Shah <aarshkshah1992@gmail.com> Co-authored-by: Adin Schmahmann <adin.schmahmann@gmail.com>
|
autonat no longer maintains its own cache separate from peerstore |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently we store every peer we've ever seen that supports AutoNAT the
peersmap. This list only grows, thus leading to memory leak. We should only store connected AutoNAT peers in memory, and offload the disconnected ones to the peerstore. This requires changes in the peerstore: https://github.com/libp2p/go-libp2p-peerstore/issues/55.The text was updated successfully, but these errors were encountered: