Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Periodical refresh of DnsNameResolver
See original GitHub issuePlease answer these questions before submitting your issue.
Original discussion: https://groups.google.com/forum/#!topic/grpc-io/wxgLgjzkR30
Currently DnsNameResolver soles relies on refresh() being called to re-resolve. refresh() currently is called only when there is a connection failure, but there are cases where refreshing is needed without connection failure, e.g., rolling deploys, or simply adding a server. We could introduce periodic refresh to DnsNameResolver.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:23 (16 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
That’s the work-around that we’re currently advertising, but honestly, I think it’s kind of a hack. We should not heve to force connection churn (and the resulting CPU overhead of a new handshake) just to get the client to re-resolve periodically. If we want the client to re-resolve periodically, I think we should just be able to tell it to do that.
/sub