You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "eric baldeschwieler (JIRA)" <ji...@apache.org> on 2007/12/28 19:11:43 UTC

[jira] Created: (HADOOP-2497) sequence file does not detect corruption in key/value lengths

sequence file does not detect corruption in key/value lengths
-------------------------------------------------------------

                 Key: HADOOP-2497
                 URL: https://issues.apache.org/jira/browse/HADOOP-2497
             Project: Hadoop
          Issue Type: Bug
            Reporter: eric baldeschwieler


From:   jason@attributor.com
Subject: Re: question on Hadoop configuration for non cpu intensive jobs - 0.15.1
Date: December 28, 2007 7:20:11 AM PST
To:   hadoop-user@lucene.apache.org

Our OOM was being caused by a damaged sequence data file. We had assumed that the sequence files had checksums, which appears to be in correct.
The deserializer was reading a bad length out of the file and trying to allocate 4gig of ram.



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


[jira] Updated: (HADOOP-2497) sequence file does not detect corruption in key/value lengths

Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sameer Paranjpye updated HADOOP-2497:
-------------------------------------

    Component/s: io

> sequence file does not detect corruption in key/value lengths
> -------------------------------------------------------------
>
>                 Key: HADOOP-2497
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2497
>             Project: Hadoop
>          Issue Type: Bug
>          Components: io
>            Reporter: eric baldeschwieler
>
> From:   jason@attributor.com
> Subject: Re: question on Hadoop configuration for non cpu intensive jobs - 0.15.1
> Date: December 28, 2007 7:20:11 AM PST
> To:   hadoop-user@lucene.apache.org
> Our OOM was being caused by a damaged sequence data file. We had assumed that the sequence files had checksums, which appears to be in correct.
> The deserializer was reading a bad length out of the file and trying to allocate 4gig of ram.

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