Description
When RetryInvocationHandler attempts to retry an UnknownHostException the hostname fails to be resolved again. The InetSocketAddress in the ConnectionId has cached the fact that the hostname is unresolvable, and when the proxy tries to setup a new Connection object with that ConnectionId it checks if the (cached) resolution result is unresolved and immediately throws.
The end result is we sleep and retry for no benefit. The hostname resolution is never attempted again.
Attachments
Issue Links
- is related to
-
HDFS-12285 Better handling of namenode ip address change
- Open
-
HADOOP-15129 Datanode caches namenode DNS lookup failure and cannot startup
- Resolved
- relates to
-
HDFS-8068 Do not retry rpc calls If the proxy contains unresolved address
- Patch Available