hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9307) BufferedFSInputStream.read returns wrong results after certain seeks
Date Thu, 14 Feb 2013 17:35:14 GMT

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

Todd Lipcon commented on HADOOP-9307:
-------------------------------------

Yea, I have a randomized test case that finds this bug within a few seconds - basically a
copy of one that I wrote for HDFS a couple years ago. Will upload it with a bugfix patch hopefully
later today, but maybe early next week (pretty busy next two days). FWIW the fix is simple
-- just need to add {{(this.pos != this.count)}} into the condition to run the seek-in-buffer
optimization
                
> BufferedFSInputStream.read returns wrong results after certain seeks
> --------------------------------------------------------------------
>
>                 Key: HADOOP-9307
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9307
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 1.1.1, 2.0.2-alpha
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>
> After certain sequences of seek/read, BufferedFSInputStream can silently return data
from the wrong part of the file. Further description in first comment below.

--
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