[
https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916304#comment-16916304
]
Li Cheng commented on HDDS-1933:
--------------------------------
[~msingh] [~elek]
As I look around, this seems relevant in kubernetes:
[https://github.com/kubernetes/dns/issues/266].
Can you try setting {{publishNotReadyAddresses=true}} in kube to see if it
resolves? This issue seems more likely to be the thing with kubernetes.
Setting DFS_DATANODE_USE_DN_HOSTNAME_DEFAULT = true is another option. Shall we
consider to use hostname as default? (current default option is IP). [~xyao]
[~Sammi] Datanode uses java DNS lookup once hostname is not explicitly set in
config in start process and ip address is retrieved from the dns hostname via
InetAddress.getHostName. So then hostname and ip address are essentially the
same with hostname being more well-rounded (Ip-ish hostname, not like
'localhost'). So I think setting hostname as the default is a viable option.
> Datanode should use hostname in place of ip addresses to allow DN's to work
> when ipaddress change
> -------------------------------------------------------------------------------------------------
>
> Key: HDDS-1933
> URL: https://issues.apache.org/jira/browse/HDDS-1933
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode, SCM
> Affects Versions: 0.4.0
> Reporter: Mukul Kumar Singh
> Priority: Blocker
>
> This was noticed by [~elek] while deploying Ozone on Kubernetes based
> environment.
> When the datanode ip address change on restart, the Datanode details cease to
> be correct for the datanode. and this prevents the cluster from functioning
> after a restart.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
