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 "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2015/02/25 17:20:06 UTC

[jira] [Updated] (HDFS-7843) A truncated file is corrupted after rollback from a rolling upgrade

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

Tsz Wo Nicholas Sze updated HDFS-7843:
--------------------------------------
    Attachment: h7843_20150226.patch

h7843_20150226.patch: use copy-on-truncate for rolling upgrade.

> A truncated file is corrupted after rollback from a rolling upgrade
> -------------------------------------------------------------------
>
>                 Key: HDFS-7843
>                 URL: https://issues.apache.org/jira/browse/HDFS-7843
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>            Priority: Blocker
>             Fix For: 2.7.0
>
>         Attachments: h7843_20150226.patch
>
>
> Here is a rolling upgrade truncate test from [~brandonli].  The basic test step is: (3 nodes cluster with HA)
> 1. upload a file to hdfs
> 2. start rollingupgrade. finish rollingupgrade for namenode and one datanode. 
> 3. truncate the file in hdfs to 1byte
> 4. do rollback
> 5. download file from hdfs, check file size to be original size
> I see the file size in hdfs is correct but can't read it because the block is corrupted.



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