Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 20D1818B02 for ; Wed, 30 Sep 2015 16:39:53 +0000 (UTC) Received: (qmail 42844 invoked by uid 500); 30 Sep 2015 16:39:21 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 42802 invoked by uid 500); 30 Sep 2015 16:39:21 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 42756 invoked by uid 99); 30 Sep 2015 16:39:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Sep 2015 16:39:21 +0000 Date: Wed, 30 Sep 2015 16:39:21 +0000 (UTC) From: "Hudson (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-7652) Process block reports for erasure coded blocks MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-7652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937629#comment-14937629 ] Hudson commented on HDFS-7652: ------------------------------ FAILURE: Integrated in Hadoop-Yarn-trunk #1203 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/1203/]) HDFS-7652. Process block reports for erasure coded blocks. Contributed (zhezhang: rev 0c1da5a0300f015a7e39f2b40a73fb06c65a78c8) * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockIdManager.java > Process block reports for erasure coded blocks > ---------------------------------------------- > > Key: HDFS-7652 > URL: https://issues.apache.org/jira/browse/HDFS-7652 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Zhe Zhang > Assignee: Zhe Zhang > Fix For: HDFS-7285 > > Attachments: HDFS-7652.001.patch, HDFS-7652.002.patch, HDFS-7652.003.patch, HDFS-7652.004.patch, HDFS-7652.005.patch, HDFS-7652.006.patch > > > HDFS-7339 adds support in NameNode for persisting block groups. For memory efficiency, erasure coded blocks under the striping layout are not stored in {{BlockManager#blocksMap}}. Instead, entire block groups are stored in {{BlockGroupManager#blockGroups}}. When a block report arrives from the DataNode, it should be processed under the block group that it belongs to. The following naming protocol is used to calculate the group of a given block: > {code} > * HDFS-EC introduces a hierarchical protocol to name blocks and groups: > * Contiguous: {reserved block IDs | flag | block ID} > * Striped: {reserved block IDs | flag | block group ID | index in group} > * > * Following n bits of reserved block IDs, The (n+1)th bit in an ID > * distinguishes contiguous (0) and striped (1) blocks. For a striped block, > * bits (n+2) to (64-m) represent the ID of its block group, while the last m > * bits represent its index of the group. The value m is determined by the > * maximum number of blocks in a group (MAX_BLOCKS_IN_GROUP). > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)