[
https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298197#comment-17298197
]
Kalan MacRow commented on HDDS-1933:
------------------------------------
[~elek] thanks for the reply, I was running the 1.0.0 manifests from
kubernetes/examples/ozone in a k8s 1.19 kind cluster. Ozone would come up and
logs etc looked fine on datanodes/scm/om, and volume and bucket creation was
working. But any other operations (eg {{freon ockg -n1000}}) would result in
the stack track mentioned on HDDS-3122. After some more digging and tweaking in
the main configmap/environment to match one of the compose tests, I've got some
freon tests passing, but suspect I'm still going to have issues with datanode
restarts.
> 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]
