[ 
https://issues.apache.org/jira/browse/HADOOP-19408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Nauroth updated HADOOP-19408:
-----------------------------------
    Description: 
HADOOP-15129 changed RPC connections so that if a client is initialized before 
the server boots, it can re-resolve DNS to discover the updated address and 
complete a successful connection. HADOOP-18365 addressed a remaining problem 
with an old IP address remaining in the {{ConnectionId}} after the retry. 
Unfortunately, this has also reintroduced the problem that HADOOP-15129 tried 
to address, because it disallows hostname changes:

{{      if (!Objects.equals(this.address.getHostName(), address.getHostName())) 
{}}
{{        throw new IllegalArgumentException("Hostname must match: " + 
this.address + " vs "}}
{{            + address);}}
{{      }}}

 

  was:
HADOOP-15129 changed RPC connections so that if a client is initialized before 
the server boots, it can re-resolve DNS to discover the updated address and 
complete a successful connection. HADOOP-18365 addressed a remaining problem 
with an old IP address remaining in the {{ConnectionId}} after the retry. 
Unfortunately, this has also reintroduced the problem that HADOOP-15129 tried 
to address, because it disallows hostname changes:

{{
      if (!Objects.equals(this.address.getHostName(), address.getHostName())) {
        throw new IllegalArgumentException("Hostname must match: " + 
this.address + " vs "
            + address);
      }
}}



> RPC clients cannot tolerate hostname changes from DNS resolution.
> -----------------------------------------------------------------
>
>                 Key: HADOOP-19408
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19408
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 3.4.0, 3.3.5
>            Reporter: Chris Nauroth
>            Priority: Major
>
> HADOOP-15129 changed RPC connections so that if a client is initialized 
> before the server boots, it can re-resolve DNS to discover the updated 
> address and complete a successful connection. HADOOP-18365 addressed a 
> remaining problem with an old IP address remaining in the {{ConnectionId}} 
> after the retry. Unfortunately, this has also reintroduced the problem that 
> HADOOP-15129 tried to address, because it disallows hostname changes:
> {{      if (!Objects.equals(this.address.getHostName(), 
> address.getHostName())) {}}
> {{        throw new IllegalArgumentException("Hostname must match: " + 
> this.address + " vs "}}
> {{            + address);}}
> {{      }}}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to