You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/01/12 20:20:45 UTC

[jira] Created: (MAPREDUCE-2258) IFile reader closes stream and compressor in wrong order

IFile reader closes stream and compressor in wrong order
--------------------------------------------------------

                 Key: MAPREDUCE-2258
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2258
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: task
    Affects Versions: 0.20.4, 0.22.0
            Reporter: Todd Lipcon
             Fix For: 0.22.0


In IFile.Reader.close(), we return the decompressor to the pool and then call close() on the input stream. This is backwards and causes a rare race in the case of LzopCodec, since LzopInputStream makes a few calls on the decompressor object inside close(). If another thread pulls the decompressor out of the pool and starts to use it in the meantime, the first thread's close() will cause the second thread to potentially miss pieces of data.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.