[
https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931834#comment-16931834
]
Siddharth Wagle commented on HDDS-1933:
---------------------------------------
We can get away with still preserving ipAddress in the yaml and also
DatanodeDetails object, I think only change needed to fix this is here:
https://github.com/apache/hadoop/blob/eefe9bc85ccdabc2b7303969934dbce98f2b31b5/hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/node/SCMNodeManager.java#L263
Currently, we rely on this flag _dfs.datanode.use.datanode.hostname_ to decide
whether to use hostname or ipAddress in order to map to DatanodeDetails.UUID
and the UUID is the system identifier already so, no downstream change should
be necessary. [~msingh]/[~elek] thoughts?
> 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: [email protected]
For additional commands, e-mail: [email protected]
