hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-7052) TestFixedLengthInputFormat#testFormatCompressedIn is flaky
Date Thu, 15 Feb 2018 23:19:00 GMT

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

Hudson commented on MAPREDUCE-7052:
-----------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13666 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/13666/])
MAPREDUCE-7052. TestFixedLengthInputFormat#testFormatCompressedIn is (jlowe: rev a53d62ab26e170a0338f93e228718da52e9196e4)
* (edit) hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/TestFixedLengthInputFormat.java


> TestFixedLengthInputFormat#testFormatCompressedIn is flaky
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-7052
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7052
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client, test
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>             Fix For: 3.1.0, 3.0.1, 2.10.0, 2.9.1, 2.8.4, 2.7.6
>
>         Attachments: MAPREDUCE-7052-001.patch, MAPREDUCE-7052-002.patch
>
>
> Sometimes the test case TestFixedLengthInputFormat#testFormatCompressedIn can fail with
the following error:
> {noformat}
> java.lang.OutOfMemoryError: Requested array size exceeds VM limit
> 	at org.apache.hadoop.mapred.TestFixedLengthInputFormat.runRandomTests(TestFixedLengthInputFormat.java:322)
> 	at org.apache.hadoop.mapred.TestFixedLengthInputFormat.testFormatCompressedIn(TestFixedLengthInputFormat.java:90)
> {noformat}
> *Root cause:* under special circumstances, the following line can return a huge number:
> {noformat}
>           // Test a split size that is less than record len
>           numSplits = (int)(fileSize/Math.floor(recordLength/2));
> {noformat}
> For example, let {{seed}} be 2026428718. This causes {{recordLength}} to be 1 at iteration
19. {{Math.floor()}} returns negative Infinity, which becomes positve infinity after the divison.
Casting it to {{int}} yields {{Integer.MAX_VALUE}}. Eventually we get an OOME because the
test wants to create a huge {{InputSplit}} array.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org


Mime
View raw message