You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2015/08/31 22:55:46 UTC

[jira] [Commented] (HDFS-5995) TestFSEditLogLoader#testValidateEditLogWithCorruptBody gets OutOfMemoryError and dumps heap.

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

Colin Patrick McCabe commented on HDFS-5995:
--------------------------------------------

Update: So, it turns out that the NameNode or JournalNode could get an {{OutOfMemoryException}} when reading a corrupt ACL operation even after the introduction of HDFS-6038.  The reason is because the patch for HDFS-6038 simply reads and discards the 4-byte length in {{readOp}}.  It doesn't actually validate it in {{readOp}}, only in {{scanOp}}.  This will be fixed in HDFS-8965.

> TestFSEditLogLoader#testValidateEditLogWithCorruptBody gets OutOfMemoryError and dumps heap.
> --------------------------------------------------------------------------------------------
>
>                 Key: HDFS-5995
>                 URL: https://issues.apache.org/jira/browse/HDFS-5995
>             Project: Hadoop HDFS
>          Issue Type: Test
>          Components: namenode, test
>    Affects Versions: 2.4.0
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>         Attachments: HDFS-5995.1.patch
>
>
> {{TestFSEditLogLoader#testValidateEditLogWithCorruptBody}} is experiencing {{OutOfMemoryError}} and dumping heap since the merge of HDFS-4685.  This doesn't actually cause the test to fail, because it's a failure test that corrupts an edit log intentionally.  Still, this might cause confusion if someone reviews the build logs and thinks this is a more serious problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)