[
https://issues.apache.org/jira/browse/HDFS-16540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767163#comment-17767163
]
David Manning commented on HDFS-16540:
--------------------------------------
[~stack] This says fixed in `branch-3.3` or `3.3.5` but the change is not
actually there. See
[https://github.com/apache/hadoop/blob/ed7aecf0e5dc63583fa8b5714b9dddfd8f14a170/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/DatanodeManager.java#L1175]
or [https://github.com/apache/hadoop/pull/4246] - I think the wrong change was
accidentally committed.
> Data locality is lost when DataNode pod restarts in kubernetes
> ---------------------------------------------------------------
>
> Key: HDFS-16540
> URL: https://issues.apache.org/jira/browse/HDFS-16540
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.3.2
> Reporter: Huaxiang Sun
> Assignee: Huaxiang Sun
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.5
>
> Time Spent: 8h 20m
> Remaining Estimate: 0h
>
> We have HBase RegionServer and Hdfs DataNode running in one pod. When the pod
> restarts, we found that data locality is lost after we do a major compaction
> of hbase regions. After some debugging, we found that upon pod restarts, its
> ip changes. In DatanodeManager, maps like networktopology are updated with
> the new info. host2DatanodeMap is not updated accordingly. When hdfs client
> with the new ip tries to find a local DataNode, it fails.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
