[
https://issues.apache.org/jira/browse/HBASE-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199531#comment-13199531
]
Zhihong Yu commented on HBASE-5319:
-----------------------------------
Maybe the test failure implies some bug.
We should include the value of cacheOnWrite in the following log:
{code}
LOG.info("Compression algorithm: " + algo + ", pread=" + pread);
{code}
>From
>https://builds.apache.org/view/G-L/view/HBase/job/HBase-TRUNK/lastCompletedBuild/testReport/org.apache.hadoop.hbase.io.hfile/TestHFileBlock/testPreviousOffset_1_/:
{code}
2012-02-02 21:52:54,017 INFO [pool-1-thread-1] hfile.TestHFileBlock(472):
Compression algorithm: GZ, pread=true
2012-02-02 21:52:55,290 INFO [pool-1-thread-1] hbase.ResourceChecker(145):
after io.hfile.TestHFileBlock#testPreviousOffset[1]: 57 threads (was 57), 77
file descriptors (was 75). 0 connections, -file handle leak?-
{code}
Looks like the OOME happened for 'Compression algorithm: GZ, pread=true,
cacheOnWrite=true'
For the above case, we have 2 options:
1. ask for access to
/home/jenkins/jenkins-slave/workspace/HBase-TRUNK/trunk/target/test-data/898f8b80-7820-4c5a-bc9b-f0fe0891bec2/prev_offset
on build machine
2. before OOME, try to dump the contents of prev_offset
We should have more clue once we get the file that causes OOME when deflating.
> TRUNK broke since hbase-4218 went in? TestHFileBlock OOMEs
> -----------------------------------------------------------
>
> Key: HBASE-5319
> URL: https://issues.apache.org/jira/browse/HBASE-5319
> Project: HBase
> Issue Type: Bug
> Reporter: stack
>
> Check it out...https://builds.apache.org/job/HBase-TRUNK/ Mikhail, you might
> know whats up. Else, will have a looksee...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
