Uploaded image for project: 'Hadoop Distributed Data Store'
  1. Hadoop Distributed Data Store
  2. HDDS-698 Support Topology Awareness for Ozone
  3. HDDS-1713

ReplicationManager fail to find proper node topology based on Datanode details from heartbeat

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.4.1
    • Component/s: None
    • Target Version/s:

      Description

      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. 

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Sammi Sammi Chen
                Reporter:
                xyao Xiaoyu Yao
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 4h
                  4h