Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 25 Feb 2015 15:27:05 +0000 (UTC)
From: "Tsz Wo Nicholas Sze (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12777561.1424877982000.11688.1424878025165@Atlassian.JIRA>
In-Reply-To: <JIRA.12777561.1424877982000@Atlassian.JIRA>
References: <JIRA.12777561.1424877982000@Atlassian.JIRA>
 <JIRA.12777561.1424877982586@arcas>
Subject: [jira] [Created] (HDFS-7843) A truncated file is corrupted after
 rollback from a rolling upgrade
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Tsz Wo Nicholas Sze created HDFS-7843:
-----------------------------------------

             Summary: 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
            Reporter: Tsz Wo Nicholas Sze
            Assignee: Tsz Wo Nicholas Sze
            Priority: Blocker


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)