hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sammi Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-699) Detect Ozone Network topology
Date Tue, 29 Jan 2019 06:24:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754644#comment-16754644

Sammi Chen commented on HDDS-699:

Hi [~szetszwo], thanks for the comments.  For the NetworkTopology performance, at the beginning
I thought most of the access are reads after the network topology is built, so a read write
reentrant single netlock approach may not cause much performance penalty. If it will really
cause big performance issue, then we'd better do some improvement. To make the InnerNode thread
soft, I intend to introduce a google component ConcurrentLinkedHashMap to replace the  ConcurrentHashMap.
The component is never used in Hadoop and it has "Apache License 2.0". I assume it's OK to
use it in Ozone. Let me know if there is other opinions.  

> Detect Ozone Network topology
> -----------------------------
>                 Key: HDDS-699
>                 URL: https://issues.apache.org/jira/browse/HDDS-699
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Xiaoyu Yao
>            Assignee: Sammi Chen
>            Priority: Major
>         Attachments: HDDS-699.00.patch, HDDS-699.01.patch
> Traditionally this has been implemented in Hadoop via script or customizable java class.
One thing we want to add here is the flexible multi-level support instead of fixed levels
like DC/Rack/NG/Node.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message