[
https://issues.apache.org/jira/browse/HDFS-16688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Vaughan updated HDFS-16688:
---------------------------------
Target Version/s: 3.4.0, 3.3.9
Affects Version/s: 3.4.0
3.3.9
> Unresolved Hosts during startup are not synced by JournalNodes
> --------------------------------------------------------------
>
> Key: HDFS-16688
> URL: https://issues.apache.org/jira/browse/HDFS-16688
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: journal-node
> Affects Versions: 3.4.0, 3.3.9
> Environment: Running in Kubernetes using Java 11, with an HA
> configuration.
> Reporter: Steve Vaughan
> Assignee: Steve Vaughan
> Priority: Major
> Labels: pull-request-available
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
