Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Resolve hostnames using netty's non-blocking DNS resolver #1517
Resolve hostnames using netty's non-blocking DNS resolver #1517
Changes from 1 commit
bb645d2
ec85577
13cd028
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Supplemental Comments]
The key point of this PR. cf: https://netty.io/news/2016/05/26/4-1-0-Final.html
If we want to use non-blocking dns resolver, we need to pass
DnsAddressResolverGroup
toBootstrap
.Also note that netty encourages users to support TCP fallback in Netty 4.1.37 release note:
https://netty.io/news/2019/06/28/4-1-37-Final.html
I followed Netty 4.1.37 release note, i.e., use
DnsNameResolverBuilder
withDatagramChannel
(UDP) andSocketChannel
(TCP).Since
Transports.socketChannelClass()
returnsClass<? extends Channel>
andDnsNameResolverBuilder#socketChannelType
wantsClass<? extends SocketChannel> channelType
,we need to cast the return value using
asSubclass
(or change the return type ofTransports#socketChannelClass
).I didn't attach a test code about this but for just in case I checked we can cast known socket channels safely like:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Supplemental Comments]
I added
resolver(...)
all places wherechannelType(...)
is used.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it makes sense to refactor the connect code a bit to pull things more together. I'll take care of this during the merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Question; nits]
For consistency with
socketChannelClass()
, is it better to declare here asClass<? extends Channel> datagramChannelClass()
?It seems a bit wired because a method for TCP returns
Channel
while a method for UDP returnsDatagramChannel
.Note that if we return
Class<? extends Channel>
here, we need cast the return value athttps://github.com/lettuce-io/lettuce-core/pull/1517/files#diff-954f0da1e02d2af777f9afc758b8b20f3f2df40a221f1a0e3569ef05402ccd97R310