[HDFS-16688] Unresolved Hosts during startup are not synced by JournalNodes

• Type: Improvement
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.4.0, 3.3.5
• Component/s: journal-node
• Labels: pull-request-available

Environment

Running in Kubernetes using Java 11, with an HA configuration.

• Target Version/s: 3.3.9
• Assignee: Steve Vaughan
• Reporter: Steve Vaughan
• Created: 25/Jul/22 15:04
• Updated: 26/Feb/23 17:58

Description

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.

Issue Links

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