You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Vinayakumar B (JIRA)" <ji...@apache.org> on 2015/04/22 07:47:58 UTC

[jira] [Updated] (HDFS-8217) During block recovery for truncate Log new Block Id in case of copy-on-truncate is true.

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

Vinayakumar B updated HDFS-8217:
--------------------------------
    Attachment: HDFS-8217-01.patch

Attached the patch. 
Please review.

> 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)