Skip to content
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

external port mappings should be cached for some time #1656

Closed
whyrusleeping opened this issue Sep 5, 2015 · 4 comments
Closed

external port mappings should be cached for some time #1656

whyrusleeping opened this issue Sep 5, 2015 · 4 comments
Labels
kind/bug A bug in existing code (including security flaws)

Comments

@whyrusleeping
Copy link
Member

currently we call out to ExternalAddrs on the nat manager way too often, we need to find a way to cache this intelligently.

@jbenet this might also explain why some nodes still have sooooo many addresses that they advertise.

@whyrusleeping whyrusleeping added the kind/bug A bug in existing code (including security flaws) label Sep 5, 2015
@jbenet
Copy link
Member

jbenet commented Sep 6, 2015

  • easy: time based caching. (maybe every 30 or 60s? packets to the nat are not very expensive)
  • harder: figure out how to ask the nat to tell us if it changes. seems hard.

@whyrusleeping
Copy link
Member Author

I think time based caching will be a good quick short term solution. This is a fairly major issue, since it crashes our most used command.

@jbenet
Copy link
Member

jbenet commented Sep 6, 2015

Indeed

@whyrusleeping
Copy link
Member Author

issue has been addressed, but the symptoms still occur for other reasons. closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws)
Projects
None yet
Development

No branches or pull requests

2 participants