Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 11 Mar 2015 06:00:46 +0000 (UTC)
From: "GAO Rui (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12778667.1425267748000.60617.1426053645995@Atlassian.JIRA>
In-Reply-To: <JIRA.12778667.1425267748000@Atlassian.JIRA>
References: <JIRA.12778667.1425267748000@Atlassian.JIRA>
 <JIRA.12778667.1425267748687@arcas>
Subject: [jira] [Updated] (HDFS-7864) Erasure Coding: Update safemode
 calculation for striped blocks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

GAO Rui updated HDFS-7864:
--------------------------
    Attachment: HDFS-7864.2.patch

safemode calculation has been modified for stripedBlock by checking wether the storedBlock is a stripedBlock by using (instanceof BlockInfoStriped)

> Erasure Coding: Update safemode calculation for striped blocks
> --------------------------------------------------------------
>
>                 Key: HDFS-7864
>                 URL: https://issues.apache.org/jira/browse/HDFS-7864
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Jing Zhao
>            Assignee: GAO Rui
>         Attachments: HDFS-7864.1.patch, HDFS-7864.2.patch
>
>
> We need to update the safemode calculation for striped blocks. Specifically, each striped block now consists of multiple data/parity blocks stored in corresponding DataNodes. The current code's calculation is thus inconsistent: each striped block is only counted as 1 expected block, while each of its member block may increase the number of received blocks by 1.


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