[ https://issues.apache.org/jira/browse/HDDS-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoyu Yao updated HDDS-1713: ----------------------------- Status: Patch Available (was: Open) > ReplicationManager fail to find proper node topology based on Datanode > details from heartbeat > --------------------------------------------------------------------------------------------- > > Key: HDDS-1713 > URL: https://issues.apache.org/jira/browse/HDDS-1713 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Reporter: Xiaoyu Yao > Assignee: Xiaoyu Yao > Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > DN does not have the topology info included in its heartbeat message for > container report/pipeline report. > SCM is where the topology information is available. During the processing of > heartbeat, we should not rely on the datanodedetails from report to choose > datanodes for close container. Otherwise, all the datanode locations of > existing container replicas will fallback to /default-rack. > > The fix is to retrieve the corresponding datanode locations from scm > nodemanager, which has authoritative network topology information. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org