[
https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058268#comment-17058268
]
Attila Doroszlai commented on HDDS-1933:
----------------------------------------
Setting {{dfs.datanode.use.datanode.hostname=true}} is not enough, because
Ozone also [uses IP for Raft peer
address|https://github.com/apache/hadoop-ozone/blob/a144ab871e5e7af0416eb0cb5143b02183336d0f/hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/ratis/RatisHelper.java#L93],
which is stored in Raft group config.
The problem can be reproduced (most of the time) even in docker-compose
environment:
{code}
cd hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT/compose/ozone
OZONE_REPLICATION_FACTOR=3 ./run.sh
<wait until leader elected>
<press Ctrl-C once for graceful shutdown>
OZONE_REPLICATION_FACTOR=3 ./run.sh
{code}
If IP addresses are shuffled by Docker during restart, datanodes will not be
able to elect leader.
> 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
