hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5581) NameNodeFsck should use only one instance of BlockPlacementPolicy
Date Tue, 03 Dec 2013 01:25:35 GMT

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

Vinay commented on HDFS-5581:
-----------------------------

Thanks Colin.

> NameNodeFsck should use only one instance of BlockPlacementPolicy
> -----------------------------------------------------------------
>
>                 Key: HDFS-5581
>                 URL: https://issues.apache.org/jira/browse/HDFS-5581
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>            Reporter: Vinay
>            Assignee: Vinay
>             Fix For: 2.4.0
>
>         Attachments: HDFS-5581.patch, HDFS-5581.patch
>
>
> While going through NameNodeFsck I found that following code creates the new instance
of BlockPlacementPolicy for every block.
> {code}      // verify block placement policy
>       BlockPlacementStatus blockPlacementStatus = 
>           BlockPlacementPolicy.getInstance(conf, null, networktopology).
>               verifyBlockPlacement(path, lBlk, targetFileReplication);{code}
> It would be better to use the namenode's BPP itself instead of creating a new one.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message