[HDFS-16684] Exclude self from JournalNodeSyncer when using a bind host

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0, 3.3.5
• Fix Version/s: 3.4.0, 3.3.5
• Component/s: journal-node
• Labels: pull-request-available

Environment

Running with Java 11 and bind addresses set to 0.0.0.0.

• Target Version/s: 3.4.0, 3.3.5
• Hadoop Flags: Reviewed
• Assignee: Steve Vaughan
• Reporter: Steve Vaughan
• Created: 25/Jul/22 14:07
• Updated: 28/Aug/22 18:16
• Resolved: 28/Aug/22 18:16

Description

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.

Issue Links

• is a child of: HADOOP-18396 Issues running in dynamic / managed environments
• links to: GitHub Pull Request #4723
• links to: GitHub Pull Request #4786