[
https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297640#comment-17297640
]
Kalan MacRow edited comment on HDDS-1933 at 3/8/21, 6:47 PM:
-------------------------------------------------------------
[~ppogde] do you know if there is a fix/workaround for this issue for 1.0.0 on
k8s? I haven't been able to get Ozone to function at all on k8s using the
example manifests and the suggestions on this thread. cc [~adoroszlai]
[~yjxxtd] [~swagle] Thanks! edit: also couldn't find any PRs related to this
issue.
was (Author: kalanm):
[~ppogde] do you know if there is a fix/workaround for this issue for 1.0.0 on
k8s? I haven't been able to get Ozone to function at all on k8s using the
example manifests and the suggestions on this thread. cc [~adoroszlai]
[~yjxxtd] [~swagle] Thanks!
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
