[
https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492961#comment-17492961
]
Shane commented on HDDS-1933:
-----------------------------
Any possibility to fix this in coming release? Or does someone have PR for it?
Without this, Ozone is not usable in Kubernetes. Basically, an Ozone cluster
can work well until there is some POD got restarted, or the Kubernetes cluster
got restarted...
> 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: Apache Ozone
> Issue Type: Bug
> Components: Ozone Datanode, SCM
> Affects Versions: 0.4.0
> Reporter: Mukul Kumar Singh
> Assignee: runzhiwang
> Priority: Major
> Labels: TriagePending
>
> 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.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
