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

   ### Description of PR
   
   The JournalNodeSyncer will include the local instance in syncing when using 
a bind host (e.g. 0.0.0.0).  There is a mechanism that is supposed to exclude 
the local instance, but it doesn't recognize the meta-address as a local 
address.
   
   Running with bind addresses set to 0.0.0.0, the JournalNodeSyncer will log 
attempts to sync with itself as part of the normal syncing rotation.  For an HA 
configuration running 3 JournalNodes, the "other" list used by the 
JournalNodeSyncer will include 3 proxies.
   
   Exclude bound local addresses, including the use of a wildcard address in 
the bound host configurations.
   
   ### How was this patch tested?
   
   An additional unit tests was added to verify the call getJournalAddrList 
dropped the current instance.
   
   Integration tests were conducted in HA configuration in Kubernetes, running 
Java 11.  After the patch, all JournalNodes stopped attempting to sync with 
themselves.
   
   ### 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