[
https://issues.apache.org/jira/browse/HDFS-16540?focusedWorklogId=770657&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-770657
]
ASF GitHub Bot logged work on HDFS-16540:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/May/22 04:32
Start Date: 16/May/22 04:32
Worklog Time Spent: 10m
Work Description: saintstack merged PR #4246:
URL: https://github.com/apache/hadoop/pull/4246
Issue Time Tracking
-------------------
Worklog Id: (was: 770657)
Time Spent: 7h (was: 6h 50m)
> 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
> Time Spent: 7h
> 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.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
