[
https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058304#comment-17058304
]
Siddharth Wagle edited comment on HDDS-1933 at 3/13/20, 12:03 AM:
------------------------------------------------------------------
DatanodeDetails are identified by unique UUID already, the problem according to
me is that NodeManager has a Map <ip -> DatanodeDetails> which can be
Map<hostname -> DatanodeDetails> which should make it ip independent based on
my previous analysis, although I have not tested this, just looked at the code
and pointed out where we use this config property to decide what should be the
key in the Map.
was (Author: swagle):
DatanodeDetails are identified by unique UUID already, the problem according to
me is that NodeManager has a Map <ip -> DatanodeDetails> which can be
Map<hostname -> DatanodeDetails> which should make it ip independent based on
my previous analysis, although I have tested this, just looked at the code and
pointed out where we use this config property to decide what should be the key
in the Map.
> 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: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
