hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6700) BlockPlacementPolicy shoud choose storage but not datanode for deletion
Date Fri, 18 Jul 2014 17:36:05 GMT

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

Arpit Agarwal commented on HDFS-6700:

+1 for the patch.

One caveat - NN storage map can be temporarily inaccurate since DN volume choosing policy
overrides NN storage choice at block creation. It does not affect this change and we should
fix the creation separately.

> BlockPlacementPolicy shoud choose storage but not datanode for deletion
> -----------------------------------------------------------------------
>                 Key: HDFS-6700
>                 URL: https://issues.apache.org/jira/browse/HDFS-6700
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>            Priority: Minor
>         Attachments: h6700_20140717.patch, h6700_20140717b.patch
> HDFS-2832 changed datanode storage model from a single storage, which may correspond
to multiple physical storage medias, to a collection of storages with each storage corresponding
to a physical storage media.
> BlockPlacementPolicy.chooseReplicaToDelete still chooses replica in term of 
> DatanodeDescriptor but not DatanodeStorageInfo.

This message was sent by Atlassian JIRA

View raw message