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

   ### Description of PR
   
   During the JournalNode startup, it builds the list of servers in the 
JournalNode set, ignoring hostnames that cannot be resolved.  In environments 
with dynamic IP address allocations this means that the JournalNodeSyncer will 
never sync with hosts that aren't resolvable during startup.
   
   Allow unresolved names during startup, so that when the hosts become 
available they will be included in JournalNode synchronization.  This also 
requires that mechanisms that return a string representation which includes the 
IP address had to be updated to handle unresolved addresses.
   
   ### How was this patch tested?
   
   Integration tests were performed against an HA configuration running in 
Kubernetes, running Java 11.  Starting the cluster with fewer replicas than the 
list of JournalNodes listed in the configurations started, and the logs showed 
attempts to sync against the missing replicas.  Missing instances of the 
JournalNode were incorporated into synchronization and NameNode shared edits 
once they were started without any intervention.
   
   ### 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