snmvaughan opened a new pull request, #4693:
URL: https://github.com/apache/hadoop/pull/4693

   
   ### Description of PR
   
   Perform a DNS reverse name lookup when getCanonicalHost() returns the IP 
address as a string.  The standard InetAddress getCanonicalHostName() has the 
following issues:
   1. It reports any cached value if exists
   2. It returns the IP address if it is unable to resolve a canonical name
   3. It caches any returned values, which would include the IP address as a 
string
   
   ### How was this patch tested?
   
   An HA configuration was deployed to Kubernetes, running Java 11.  All 
services startup as expected.  Performing a rolling restart of the JournalNodes 
caused failures when the NameNode communicated with the newly started 
JournalNode, reporting an exception that included a principal with the IP 
address instead of the canonical host name.
   
   Performing the same activity after applying the patch succeeds as the DNS 
reverse lookup is performed to acquire the correct calculated principal.  
   
   ### For code changes:
   
   - [X] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to