Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 6 Jun 2011 20:18:59 +0000 (UTC)
From: "Ramkumar Vadali (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <303440627.1721.1307391539167.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (MAPREDUCE-2570) Bug in RAID FS
 (DistributedRaidFileSystem) unraid path
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Bug in RAID FS (DistributedRaidFileSystem) unraid path
------------------------------------------------------

                 Key: MAPREDUCE-2570
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2570
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: contrib/raid
            Reporter: Ramkumar Vadali
            Assignee: Ramkumar Vadali


The "un-raid" path in DistributedRaidFileSystem goes through RaidNode.unRaidCorruptBlock(), which has a bug when the parity file is inside a HAR. The temporary file that contains the recovered block contents is created in the filesystem that hosts the parity file. In case the parity file is inside a HAR, its filesystem is HarFileSystem, which is read-only. In this case the temporary file creation will fail. The fix is a one-line change to use the underlying filesystem of the HAR.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira