hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1855) fsck should verify block placement
Date Fri, 12 Oct 2007 21:39:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534416

Hairong Kuang commented on HADOOP-1855:

The code looks good except for two more comments:
1. ReplicationTargetChooser.verifyBlockPlacement does not need to take NetworkTopology as
a parameter because Class ReplicationTargetChooser has a field clusterMap that stores the
dfs network topology.
2.In  verifyBlockPlacement, is it more memory efficent if we use HashSet rather than TreeSet?

> fsck should verify block placement
> ----------------------------------
>                 Key: HADOOP-1855
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1855
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.14.2
>            Reporter: dhruba borthakur
>            Assignee: Konstantin Shvachko
>             Fix For: 0.16.0
>         Attachments: FsckBlockPlacement.patch
> fsck currently detects missing and under-replicated blocks. It would be helpful if it
can also detect blocks that do not conform to the block placement policy. An administrator
can use this tool to verify that blocks are distributed across racks.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message