hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3833) TestDFSShell fails on Windows due to file concurrent read write
Date Fri, 31 Aug 2012 17:41:08 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446164#comment-13446164
] 

Suresh Srinivas commented on HDFS-3833:
---------------------------------------

+1 for the patch.
                
> 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
>         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.<init>(FileOutputStream.java:194)
> 	at java.io.FileOutputStream.<init>(FileOutputStream.java:145)
> 	at java.io.PrintWriter.<init>(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

Mime
View raw message