You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Steve Vaughan (Jira)" <ji...@apache.org> on 2022/08/08 15:11:00 UTC

[jira] [Assigned] (HDFS-16688) Unresolved Hosts during startup are not synced by JournalNodes

     [ https://issues.apache.org/jira/browse/HDFS-16688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Vaughan reassigned HDFS-16688:
------------------------------------

    Assignee: Steve Vaughan

> 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
>         Environment: Running in Kubernetes using Java 11, with an HA configuration.
>            Reporter: Steve Vaughan
>            Assignee: Steve Vaughan
>            Priority: Major
>
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org