[ https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16910966#comment-16910966 ]
Li Cheng commented on HDDS-1933: -------------------------------- [~msingh] I was trying to reproduce it thru UT. Tried using PowerMokito in TestMiniOzoneCluster to mock fake IP address locally to trigger this, but encountered with issues. Addding PowerMockIgnore "javax.management.*" leads to javax.security.auth.login.LoginExceptiom, but not having it leads to loader constraint violation. Looks like PowerMock in MiniOzoneCluster might not be a good idea. Any thoughts on reproducing this issue in UT? > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org