[
https://issues.apache.org/jira/browse/HBASE-8855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698586#comment-13698586
]
stack commented on HBASE-8855:
------------------------------
Patch does not fix root cause (I spent time trying to fix hadoop2 builds on ec2
build but no combo would work there and it is crazy that our code takes 1G of
permgen.. something badly broke).
> TestTableInputFormatScan1/2 fail semi-silently with the hadoop 2 profile
> ------------------------------------------------------------------------
>
> Key: HBASE-8855
> URL: https://issues.apache.org/jira/browse/HBASE-8855
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.8, 0.95.1
> Reporter: Jean-Daniel Cryans
> Attachments: 8855.patch
>
>
> It looks like TestTableInputFormatScan1 and TestTableInputFormatScan2 never
> complete and surefire doesn't complain about it. Sure, you may see this:
> {noformat}
> Tests run: 6, Failures: 5, Errors: 1, Skipped: 0, Time elapsed: 269.036 sec
> <<< FAILURE!
> org.apache.maven.surefire.util.SurefireReflectionException: ...
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> Caused by: java.lang.OutOfMemoryError: PermGen space
> org.apache.maven.surefire.booter.SurefireBooterForkException: Error occurred
> in starting fork, check output in log
> ...
>
> testScanEmptyToBBA(org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScan1)
>
> testScanEmptyToBBB(org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScan1)
>
> testScanEmptyToOPP(org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScan1)
>
> testScanEmptyToEmpty(org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScan1)
> {noformat}
> But then:
> {noformat}
> [INFO] HBase - Server .................................... SUCCESS
> [10:59.929s]
> {noformat}
> This is on my machine. On our local jenkins it's leaking and the processes
> never die. And this is only with Hadoop 2. It also looks like other tests are
> failing with PermGen space.
--
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
