Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F0BFADC9D for ; Fri, 31 Aug 2012 20:50:10 +0000 (UTC) Received: (qmail 21465 invoked by uid 500); 31 Aug 2012 20:50:10 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 21433 invoked by uid 500); 31 Aug 2012 20:50:10 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 21424 invoked by uid 99); 31 Aug 2012 20:50:10 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Aug 2012 20:50:10 +0000 Date: Sat, 1 Sep 2012 07:50:10 +1100 (NCT) From: "Suresh Srinivas (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <2135337299.24771.1346446210581.JavaMail.jiratomcat@arcas> In-Reply-To: <792967382.37932.1345592918316.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (HDFS-3833) TestDFSShell fails on Windows due to file concurrent read write MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-3833: ---------------------------------- Fix Version/s: 2.2.0-alpha 1-win 3.0.0 > TestDFSShell fails on Windows due to file concurrent read write > --------------------------------------------------------------- > > Key: HDFS-3833 > URL: https://issues.apache.org/jira/browse/HDFS-3833 > Project: Hadoop HDFS > Issue Type: Bug > Components: test > Affects Versions: 3.0.0, 1-win > Reporter: Brandon Li > Assignee: Brandon Li > Fix For: 3.0.0, 1-win, 2.2.0-alpha > > Attachments: HDFS-3833.branch-1-win.patch, HDFS-3833.patch > > > TestDFSShell sometimes fails due to the race between the write issued by the test and blockscanner. Example stack trace: > {noformat} > Error Message > c:\A\HM\build\test\data\dfs\data\data1\current\blk_-7735708801221347790 (The requested operation cannot be performed on a file with a user-mapped section open) > Stacktrace > java.io.FileNotFoundException: c:\A\HM\build\test\data\dfs\data\data1\current\blk_-7735708801221347790 (The requested operation cannot be performed on a file with a user-mapped section open) > at java.io.FileOutputStream.open(Native Method) > at java.io.FileOutputStream.(FileOutputStream.java:194) > at java.io.FileOutputStream.(FileOutputStream.java:145) > at java.io.PrintWriter.(PrintWriter.java:218) > at org.apache.hadoop.hdfs.TestDFSShell.corrupt(TestDFSShell.java:1133) > at org.apache.hadoop.hdfs.TestDFSShell.testGet(TestDFSShell.java:1231) > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira