Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 23 Nov 2015 23:50:11 +0000 (UTC)
From: "Zhe Zhang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12910853.1446759882000.168632.1448322611196@Atlassian.JIRA>
In-Reply-To: <JIRA.12910853.1446759882000@Atlassian.JIRA>
References: <JIRA.12910853.1446759882000@Atlassian.JIRA>
 <JIRA.12910853.1446759882373@arcas>
Subject: [jira] [Commented] (HDFS-9386) Erasure coding:
 updateBlockForPipeline sometimes returns non-striped block for striped file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Zhe Zhang commented on HDFS-9386:
---------------------------------

Unfortunately I haven't been able to reproduce this recently. I'll try to add some more assertions and hopefully that will catch it.

> Erasure coding: updateBlockForPipeline sometimes returns non-striped block for striped file
> -------------------------------------------------------------------------------------------
>
>                 Key: HDFS-9386
>                 URL: https://issues.apache.org/jira/browse/HDFS-9386
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: erasure-coding
>    Affects Versions: 3.0.0
>            Reporter: Zhe Zhang
>
> I've seen this bug a few times. The returned {{LocatedBlock}} from {{updateBlockForPipeline}} is sometimes not {{LocatedStripedBlock}}. However, {{FSNamesystem#bumpBlockGenerationStamp}} did return a {{LocatedStripedBlock}}. Maybe a bug in PB. I'm still debugging.


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