[ 
https://issues.apache.org/jira/browse/HDFS-16540?focusedWorklogId=770312&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-770312
 ]

ASF GitHub Bot logged work on HDFS-16540:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/May/22 18:12
            Start Date: 13/May/22 18:12
    Worklog Time Spent: 10m 
      Work Description: saintstack commented on PR #4246:
URL: https://github.com/apache/hadoop/pull/4246#issuecomment-1126312782

   Two failures:
   
   TestBPOfferService.testMissBlocksWhenReregister
   TestUnderReplicatedBlocks.testSetRepIncWithUnderReplicatedBlocks
   
   They come up often enough. Let me try again. Meantime running locally.
   
   




Issue Time Tracking
-------------------

    Worklog Id:     (was: 770312)
    Time Spent: 6h 10m  (was: 6h)

> 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: 6h 10m
>  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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to