[
https://issues.apache.org/jira/browse/HBASE-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664429#action_12664429
]
Andrew Purtell commented on HBASE-1127:
---------------------------------------
+1
IMHO blockcache should be off by default, except for meta, where HBase can
clearly establish a benefit. Otherwise, it's up to the application to decide if
sufficient benefit is derived to offset the risk of the added heap pressure.
Many applications of the archival type will not benefit from blockcache on
their tables, for example.
> OOME running randomRead PE
> --------------------------
>
> Key: HBASE-1127
> URL: https://issues.apache.org/jira/browse/HBASE-1127
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Blocker
> Fix For: 0.19.0
>
>
> Blockcache is misbehaving on TRUNK. Something is broke. We OOME about 20%
> into the randomRead test. Looking at heap, its all soft references.
> Instrumenting the referencequeue, we're never clearing full gc'ing.
> Something is off.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
