[
https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932361#comment-16932361
]
Sammi Chen commented on HDDS-1933:
----------------------------------
Hi [~msingh] , offer user the option to choose IpAddress or Hostname as the
datanode identity is a tradition in HDFS. We borrow the idea from HDFS so that
Ozone can be easily adopted in the network environment where previous HDFS is
deployed. In many DCs, static IP is used for datanode. It's save to use
IpAddres as the datanode identity in the case. I would propose to keep this
option for user. If the cluster is using hostname because Ipaddress may change
after restart, like Kubernetes cluster, user can simply set
"dfs.datanode.use.datanode.hostname" to true (by default is false).
> 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.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
