[ 
https://issues.apache.org/jira/browse/HDFS-11530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948903#comment-15948903
 ] 

Yiqun Lin commented on HDFS-11530:
----------------------------------

Thanks [~vagarychen] for the comments.
I take some time to looked into this. I picked up one other type test failure 
{{TestDatanodeRegistration#testChangeIpcPort}} to have a debug. The removing 
node operation is failed if the node registers to namenode again with different 
node name. Maybe this test failure leads other test failed.
[~vagarychen], could you share your thought of this or we can file a new JIRA 
to have a track to cover this case? It seems there are still some works we 
should do before making {{DFSNetworkTopology}} as the default NetworkTopology 
{{NetworkTopology}}.

In addition, I am thinking if we use {{DFSNetworkTopology}} as the default 
class, is that mean the other subclass of {{NetworkTopology}}(e.g. 
NetworkTopologyWithNodeGroup) will be not allowed used in HDFS?

> Use HDFS specific network topology to choose datanode in 
> BlockPlacementPolicyDefault
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-11530
>                 URL: https://issues.apache.org/jira/browse/HDFS-11530
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Yiqun Lin
>            Assignee: Yiqun Lin
>         Attachments: HDFS-11530.001.patch, HDFS-11530.002.patch
>
>
> The work for {{chooseRandomWithStorageType}} has been merged in HDFS-11482. 
> But this method is contained in new topology {{DFSNetworkTopology}} which is 
> specified for HDFS. We should update this and let 
> {{BlockPlacementPolicyDefault}} use the new way since the original way is 
> inefficient.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to