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

P2P: Resolve endpoints on re-connect attempts #525

Open
heifner opened this issue Aug 12, 2024 · 2 comments · Fixed by #825, #826, #840, #841 or #853
Open

P2P: Resolve endpoints on re-connect attempts #525

heifner opened this issue Aug 12, 2024 · 2 comments · Fixed by #825, #826, #840, #841 or #853
Assignees
Labels
bug The product is not working as was intended. 👍 lgtm OCI Work exclusive to OCI team
Milestone

Comments

@heifner
Copy link
Member

heifner commented Aug 12, 2024

Currently net_plugin resolves endpoints at startup and then reuses the tcp::resolver::results_type for any re-connection attempt. If resolve fails at startup then the resolve is not attempted again. Also net_plugin reports an unhelpful "Element not found` error.

See #523 (comment)

@heifner
Copy link
Member Author

heifner commented Aug 14, 2024

You do get a warn message on the first resolve, but since it never attempts the resolve again you only get the warn message once.

warn  2024-08-14T13:19:55.590 net-2     net_plugin.cpp:4638           operator()           ] Unable to resolve p2p.spring-beta.jungletestnet.io:9898 Host not found (authoritative)

@spoonincode
Copy link
Member

fwiw, (depending on complexity of course) imo a fix for this should go in to stable release. It prevents the ability to do basic failover approaches via low TTL DNS records since clients won't see the updated record.

@bhazzard bhazzard added this to the Spring v1.0.2 milestone Sep 20, 2024
@bhazzard bhazzard added bug The product is not working as was intended. 👍 lgtm and removed triage labels Sep 20, 2024
@heifner heifner added the OCI Work exclusive to OCI team label Sep 25, 2024
@heifner heifner linked a pull request Sep 26, 2024 that will close this issue
@arhag arhag reopened this Sep 30, 2024
@spoonincode spoonincode reopened this Sep 30, 2024
heifner added a commit that referenced this issue Oct 1, 2024
@arhag arhag modified the milestones: Spring v1.0.2, Spring v1.0.3 Oct 1, 2024
@heifner heifner linked a pull request Oct 1, 2024 that will close this issue
heifner added a commit that referenced this issue Oct 1, 2024
heifner added a commit that referenced this issue Oct 1, 2024
heifner added a commit that referenced this issue Oct 1, 2024
heifner added a commit that referenced this issue Oct 2, 2024
@heifner heifner linked a pull request Oct 2, 2024 that will close this issue
heifner added a commit that referenced this issue Oct 2, 2024
heifner added a commit that referenced this issue Oct 2, 2024
heifner added a commit that referenced this issue Oct 2, 2024
heifner added a commit that referenced this issue Oct 2, 2024
spoonincode added a commit that referenced this issue Oct 2, 2024
[1.0.2 -> main] P2P: Resolve on reconnect
heifner added a commit that referenced this issue Oct 2, 2024
heifner added a commit that referenced this issue Oct 2, 2024
@arhag arhag reopened this Oct 2, 2024
heifner added a commit that referenced this issue Oct 3, 2024
heifner added a commit that referenced this issue Oct 3, 2024
heifner added a commit that referenced this issue Oct 3, 2024
heifner added a commit that referenced this issue Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment