Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 9 Mar 2015 05:36:38 +0000 (UTC)
From: "Walter Su (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12767571.1421275057000.34661.1425879398926@Atlassian.JIRA>
In-Reply-To: <JIRA.12767571.1421275057000@Atlassian.JIRA>
References: <JIRA.12767571.1421275057000@Atlassian.JIRA>
 <JIRA.12767571.1421275057391@arcas>
Subject: [jira] [Commented] (HDFS-7613) Block placement policy for erasure
 coding groups
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Walter Su commented on HDFS-7613:
---------------------------------

This jira is implemented by HDFS-7891 and HDFS-7068
1. add a BlockPlacementPolicyFaultTolerant class in HDFS-7891
2. We can make striped files use BlockPlacementPolicyFaultTolerant in HDFS-7068
It is what I think the implementation of this jira should be. Maybe it's not good enough. I have submitted the first version of patches for above two jiras. I'm really looking forword to some suggestions.

> Block placement policy for erasure coding groups
> ------------------------------------------------
>
>                 Key: HDFS-7613
>                 URL: https://issues.apache.org/jira/browse/HDFS-7613
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Zhe Zhang
>            Assignee: Walter Su
>
> Blocks in an erasure coding group should be placed in different failure domains -- different DataNodes at the minimum, and different racks ideally.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)