[
https://issues.apache.org/jira/browse/HDDS-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755460#comment-16755460
]
Tsz Wo Nicholas Sze commented on HDDS-699:
------------------------------------------
Two suggestions:
# Move the root level locking to the second level. The root node does not
cache aggregate information so that write lock at root is needed only when the
second level is changed. Each node in the second level maintain a lock to
protect its subtree.
# Separate the NetworkTopology interface and implementation so that replacing
the implementation in the future becomes possible.
#2 may not be easy. If we have #2, I am fine with any implementation today.
> 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
(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
