Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 24 Apr 2015 06:37:41 +0000 (UTC)
From: "Vinayakumar B (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12822907.1429679828000.15328.1429857461121@Atlassian.JIRA>
In-Reply-To: <JIRA.12822907.1429679828000@Atlassian.JIRA>
References: <JIRA.12822907.1429679828000@Atlassian.JIRA>
 <JIRA.12822907.1429679828032@arcas>
Subject: [jira] [Commented] (HDFS-8217) During block recovery for truncate
 Log new Block Id in case of copy-on-truncate is true.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinayakumar B commented on HDFS-8217:
-------------------------------------

Removed the .02 patch to not to confuse further

> During block recovery for truncate Log new Block Id in case of copy-on-truncate is true.
> ----------------------------------------------------------------------------------------
>
>                 Key: HDFS-8217
>                 URL: https://issues.apache.org/jira/browse/HDFS-8217
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>            Reporter: Vinayakumar B
>            Assignee: Vinayakumar B
>         Attachments: HDFS-8217-01.patch
>
>
> During the block recovery for the truncate, include the newblock Id in case copy-on-truncate set to true.
> Current log message is just as below.
> {noformat}NameNode at /127.0.0.1:55036 calls recoverBlock(BP-409377067-xx.xx.xx.253-1429679063755:blk_1073741825_1001, targets=[DatanodeInfoWithStorage[127.0.0.1:55045,null,null]], newGenerationStamp=1002){noformat}


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