[
https://issues.apache.org/jira/browse/HADOOP-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854102#action_12854102
]
sam rash commented on HADOOP-6679:
----------------------------------
1. ah yes, I see the --no-prefix option. I'll update and post the patch
2. my understanding is the jvm caches on successful resolution, not on failure,
so a retry should be useful
http://java.sun.com/javase/6/docs/technotes/guides/net/properties.html#nct
Do I misunderstand the docs?
3. you mean you want a port/service description passed in here?
public static InetSocketAddress createWithResolveRetry(
String hostname,
int port,
String portDescription
) {
....
and I assume the NetUtils.createSocketAddr() would now have to take this? It's
current signature is
public static InetSocketAddress createSocketAddr(String target,
int defaultPort) {
can you clarify what you mean by this?
> add retry logic to NetUtils.createSocketAddr() when hostname resolution fails
> -----------------------------------------------------------------------------
>
> Key: HADOOP-6679
> URL: https://issues.apache.org/jira/browse/HADOOP-6679
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 0.20.0
> Reporter: sam rash
> Priority: Minor
> Attachments: HADOOP-6679-patch-1.txt
>
>
> transient DNS errors can cause the InetSocketAddress created in
> NetUtils.createSocketAddr() to be unresolved when the hostname is resolvable.
> Add a single retry after a short sleep using a simple
> InetSocketAddressFactory class
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
